WICE Wiki v2.97 - User contributions [en]

Preview data

2018-06-28T14:37:56Z

Richard.wecke: /* Changes made in 2.48 */

[[File:Preview data.png|thumb|400x400px|Figure x: The preview data window.|link=https://wiki.alkit.se/index.php/File:Preview_data.png]]This is a tool used to graph signal values from MDF-files.

== Example of usage ==
One of the main functions is to view signals as graphs and see their route. To do so you need to select signal(s) from the file(s) you want. You select signals to the right where you see the list of signals. That list of signals is specific for the selected file. You can change which file you want signals from in the box "file viewer" on the left. Note that the files to the left are the files you had selected when clicking "Preview data". The selected signals can then be seen in the bottom under the tab "Signal preview" where you will see a quick preview of how their graph looks. By dragging the previewed signal(s) to the "Master signal preview" in the middle you can see a more extended version of the signal graph.

== Functionality ==

=== Preview modes ===
"Master signal preview" has 3 preview modes that you can select in the bottom left corner of the "Master signal preview" area. The pre-selected view is with one graph on the left and a map on the right where the signals' routes will be shown. You can also select so that instead of a map it will show a second plot or so it only shows one plot.

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

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

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

=== Map ===
When clicking on a point in the graph you will see where the car was for that given time value on the map. Note that this only works if such GPS data is available.

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

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

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

=== Quick selection mode ===
See "new in 2.46".

== New in 2.46 ==
In 2.46 you have the option to use a separate selection mode. This selection mode is called "Quick mode", and it allows you preview the same set of signals from an array of files more easily. Here is how it works:
# Select the files that you want to preview as usual and click "Preview data".
# Beneath the source list you will find a checkbox that says "Quick selection mode". Click it.
# Select a file by clicking on a file in the source list.
# Select any number of signals in the signal list.
# If you want to add any of the signals into the master preview, then do so by dragging and dropping the thumbnails as usual.
# You can now swap between files by selecting any file you like from the source list. When you swap file the signals you selected previously will now be selected again in the new file.
'''Notice: This will only work if both files have signals with the exact same name. Any deviation in signal naming will cause the program to not be able to find the signal, thus skipping it and moving on to the next signal.'''

== Changes made in 2.48 ==
As of version [[New in v2.48|2.48]], some changes has been made to previewing data.

New or changed features are :
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

New in v2.48

2018-06-28T14:37:36Z

Richard.wecke: /* Added functionality to MDF preview/monitor */

This page lists new and changed features in version 2.48 of the WICE Portal.

== Strict resource groups ==
Strict resource groups have been added to help manage measurement on large fleets of vehicles with minimum micromanagement.

== WCU as Wi-Fi Access Point ==
A WCU can now be configured to act as a Wi-fi Access Point (see [[WCU as WiFi Access Point|WCU as Wi-Fi Access Point]])

== Stopping assignments ==
Stopping of assignments in the Tasks tab have been reworked to be more intuitive and work with strict resource groups (see [[The Portal User View#Stopping assignments|stopping assignments]]).

== Canrecorder ==
Canrecorder now supports up to 6 CAN buses with CAN frame filters per CAN bus. For a closer look at how to set up a Canrecorder task, see [[The Portal User View#CAN-recorder|The Portal User View]]

== Default CAN channel should now be visible in the interface for IDC, SoH,SWDL and VinReader. ==
Users can now set a default CAN bus (Default CAN channel), on which request from the assignments are sent to. The actual CAN buses are selected from the Configuration. The settings can be found in each respective tool (found in the Modules panel).

== Support for WCU reporting back the status for its configurations ==
The WCU can now report the result of updating both the tool-configuration as well as the WCU-configuration, back to the user. The different statuses for updating are: Ok, Warning or Error. Additional text can be added, shown when hovering the mouse pointer over the status indicator.

== Added functionality to MDF preview/monitor ==
New or changed features are :
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

== Possible to search for empty fields in the Vehicles panel ==
It is now possible to search for empty fields in the Vehicles panel by entering the regular expression "^$". Any field that is a string can be searched this way except for VIN and VCU ID.

== Improved IDC-assignment CAN mapping ==
It is now possible to:
* Map all rows to one CAN bus.
* Select a partial amount of all rows and map them to one CAN bus.

== Resources can now be moved directly between resource groups ==
It is now possible to move resources between resource groups without having to first remove them from the resource group they currently belong to. Users can simply mark the resources they wish to move and press the "Add resource to resource group" button. A dialog will appear informing that resources will be removed from the group they currently belong to. By pressing "OK", the transaction will complete and the resources will be moved to the desired resource group. See [[The Portal Administrator View#Resource Groups|The Administrator Portal View]] for more.

== Support for Video preview ==
To learn more about configuring the Video module and creating Video assignments, see the [[WICE video|page about WICE Video]].

== Support for searching with the AND operator between labels ==
Users can use search expressions containing the operator AND when searching via labels.

== Get the resource group from contained member ==
Users can search out the resource group that a resource belongs to, in the Vehicles panel.

Preview data

2018-06-28T14:36:40Z

Richard.wecke:

[[File:Preview data.png|thumb|400x400px|Figure x: The preview data window.|link=https://wiki.alkit.se/index.php/File:Preview_data.png]]This is a tool used to graph signal values from MDF-files.

== Example of usage ==
One of the main functions is to view signals as graphs and see their route. To do so you need to select signal(s) from the file(s) you want. You select signals to the right where you see the list of signals. That list of signals is specific for the selected file. You can change which file you want signals from in the box "file viewer" on the left. Note that the files to the left are the files you had selected when clicking "Preview data". The selected signals can then be seen in the bottom under the tab "Signal preview" where you will see a quick preview of how their graph looks. By dragging the previewed signal(s) to the "Master signal preview" in the middle you can see a more extended version of the signal graph.

== Functionality ==

=== Preview modes ===
"Master signal preview" has 3 preview modes that you can select in the bottom left corner of the "Master signal preview" area. The pre-selected view is with one graph on the left and a map on the right where the signals' routes will be shown. You can also select so that instead of a map it will show a second plot or so it only shows one plot.

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

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

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

=== Map ===
When clicking on a point in the graph you will see where the car was for that given time value on the map. Note that this only works if such GPS data is available.

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

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

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

=== Quick selection mode ===
See "new in 2.46".

== New in 2.46 ==
In 2.46 you have the option to use a separate selection mode. This selection mode is called "Quick mode", and it allows you preview the same set of signals from an array of files more easily. Here is how it works:
# Select the files that you want to preview as usual and click "Preview data".
# Beneath the source list you will find a checkbox that says "Quick selection mode". Click it.
# Select a file by clicking on a file in the source list.
# Select any number of signals in the signal list.
# If you want to add any of the signals into the master preview, then do so by dragging and dropping the thumbnails as usual.
# You can now swap between files by selecting any file you like from the source list. When you swap file the signals you selected previously will now be selected again in the new file.
'''Notice: This will only work if both files have signals with the exact same name. Any deviation in signal naming will cause the program to not be able to find the signal, thus skipping it and moving on to the next signal.'''

== Changes made in 2.48 ==
As of version [[New in v2.48|2.48]], some changes has been made to previewing data.

You can now:
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

Tasks Tab

2018-06-28T14:22:28Z

Richard.wecke: /* The Result Section */

<includeonly>= Tasks Tab=</includeonly>
<div class="keywords"> Regexp, regex, reg ex, regual expression </div>
[[File:Illustration14.png|thumb|The search panel for finding tasks.]]
In the Tasks tab you can search for tasks, view and manage their assignments, see the log files, access result data files, and much more.

==The Search Fields Section==
The search field section consists of different columns where most have a field where you can insert search criteria to find active tasks. As an example you have the label “Task ID:” which searches the field for task IDs matching your search criteria. When searching for tasks you can fill in one or more columns where the different search criteria will be treated with a logical AND between each other.

There are many different columns: in some you can fill in a search criteria and some you can not. Below is a table with all the columns followed by a short description. Note that the columns with a star are the ones where you can enter a search criteria to filter results.
{| class="wikitable"
!Task ID*
|The nummeric Task ID.
|-
!Assignment*
|The assignment name.
|-
!Type*
|Different options for assignment types where one or more can be selected.
|-
!WCU ID*
|The WCU's ID and also the column where you see the WCU's label.
|-
!Upload size
|The upload size of all the assignment's uploads given in Kbytes.
|-
!Plate number*
|The car's plate number.
|-
!Status*
|Different options for assignment statuses where one or more can be selected.
|-
!Last log
|When the last log file was transferred to the portal.
|-
!Last upload
|Date of the assignments's last upload.
|-
!VIN*
|The car's Vehicle Identification Number.
|-
!Proto number*
|The proto number.
|-
!Project*
|The project ID.
|-
!TSU*
|The TSU ID.
|-
!Car comment*
|The car's comment/description.
|-
!Series*
|The series attribute.
|-
!Message*
|The assignment's status message.
|-
!WCU name*
|The name of the WCU.
|-
!Task owner
|The current owner of the task.
|-
!Expire date
|The date the assignment will expire.
|-
!Task creator
|The original creator of the task.
|-
!Creation date
|The creation date of the assignment.
|-
!Resource group*
|The resource group the WCU is part of.
|}
In each searchable column you can use regular expressions for your searches. To designate an "all" search you enter a period (".") for that particular field or leave it empty if another field is already filled in. All searches are treated with the letters as wild-cards. An example is if you intend to search for tasks containing the word “bear” simply enter “bear” in the text field. Now, if there are tasks with the names “bear”, “polar bear”and “unbearable” all of these will match as they contain the word “bear” somewhere.

To search for a range of WCUs, let's say the WCUs MM-810:1 – MM-823:1, you can enter the query 81[0-9]|82[0-3]. This is a regular expression where the first expression, 81[0-9], means that we want our search to start with an '8' followed by a '1' and then any digit in range 0-9. The second part, 82[0-3], means an '8' followed by a '2' and then any digit in range 0-3. The two expressions are combined with a pipe characater ("|") which means logical OR. In other words we are looking for range 810-819 OR 820-823.

'''Note!''' If your WCU/resource group you are searching for has special characters (like '(' or '/') in its name you may need to escape these characters in order to get the desired result. Escape means putting a '\' before the special character. For example if you want to enter (and search for) the resource group name 'ABC(Alpha_Bravo_Charlie)' you need to write 'ABC$Alpha\_Bravo\_Charlie$'. Another example is when you want to list a WCU that contains "07-51" in its name. In this case you need to type "07\-51", otherwise the "-" character will make the searcher to search for a range of numbers.

For more info how to use regular expressions, see [https://en.wikipedia.org/wiki/Regular_expression#Standards Regular Expressions]

When you are filling in search criteria you can see in the top right corner how WICE says "Rows found:". That tell you how many assignments your search will find so you know if you need to narrow or broaden your search.

In the bottom right corner you have two binoculars. With these you can save and load your search criterias and shown columns for future uses. You can also set a view of criteria and columns as your default by hovering over the view you want and then pressing the pin button. There is also two magnifying glasses that can save and load your search results so even if their information change and can not be found with the same search criteria you can still find them. You can also pair a search with a view by going to your searches and then on the search click the binocular button and select which view you want to pair it with. You can also pair them going to your searches and press "Select search views" where you get a window with the option to pair your searches with views.

If you are using an older version than 2.45.0 you have 4 bars with calanders to the right of them. This is a function to search assignments by date of creation and last update. This function has been removed in 2.45.0 and does not work like intended in 2.44.8.

In 2.45.0 and forward there will at the top be a option to search assignments after their label. By selecting multiple labels you can search for more than one at the same time.

== The Result Section ==
The assignments are fetched when you press the "Search" button in the Tasks tab. Here we will go through the bottom part of the Tasks tab and the options for your previous search.
===Assignment Options===
You can right-click one or many assignments to get a menu with a range of options described below:
* "Show task description" will show you the description of the task that the assignment you right-clicked on belongs to.
* "Go to Vehicles Panel" will take you to the vehicles tab. When you are in the vehicles tab the car(s) you selected will be shown in the vehicles tab.
* "Go to Search Panel" will take you to the search tab. When you are in the search tab the WCU(s) you selected will be selected in the search tab.
* "Get/Show assignment" will give you a small pop-up dialog with some assignment information and a "Download assignment" button if a download is possible. If you choose to press "Download assignment" the assignment file will be downloaded to your computer in its original format.
* "Edit task" will give you the option to edit ownership and expiration date of the task. It will also show you the WCU(s) the task is running on.
* "Show car info" and "Show WCU info" will give you a pop-up showing you available info of the assignment car and WCU. Depending on which car/WCU you choose there will be different information available since cars/WCUs can lack information.
* "Show message" will show you the assignment's status message.
* "Plot route" will open a map in your current window. In that map you can see up to 100 of the cars registered positions during the last 24 hours or the last 100 registered positions. For more information about this read [[Plot Route Dialog]].

* "Event subscription" is an option where you choose to subscibe to a car, a WCU or an assignment. When hovering above "Event subscription" you will see three options, "Connect", "Assignment status" and "Result upload". With the option "Connect " you can subscribe to the selected car(s) or WCU(s) and get notified when their connection status changes. "Assignment status" and "Result upload" subscribes you to selected assignment(s) and gets you notified about status changes and when results are uploaded. You will se events when clicking on the bell symbol at the top which gets a red dot when theres new events from your subscriptions.

===Column Options===
The result section has many ways to sort, view and handle the result with the columns. When right-clicking a column you will get a window with different options for the column.
* "Sort Ascending" and "Sort Descending" will sort the assignments in ascending or descending order after the column's attribute.
* "Configure Sort" where you can add more levels of sorting so that it sorts for more than one thing in different priority. For example can you sort after task ID ascending and then sort after WCU ID descending. When a column has a sorting prefrens the option "Clear Sort" will appear which clears your sorting preferences for that column.
* "Columns" opens a window where you can select which columns you want shown and which you want hidden by checking or unchecking their corresponding checkboxes. If you remove a column with a filled search criteria that criteria will still matter when you make a new search. Also when you make the new search the column will reappear.
* "Group by" groups together the assignments that share the column's attribute value. When they are grouped there will be the option "Ungroup" that ungroups them.
* "Freeze" moves the column to the left corner and freezes it in position so it can be rearranged. If there is alraedy a frozen column till will move next to it as they go from left to right in chronological order. The "freeze" then becomes "Unfreeze" which revertes the freeze.
* "Export to excel" will export the columns and results into an excel file that will get downloaded.
* "Clear all fields" will clear all columns of their criteria.
* "Get help for this column" should take you here.

===Get result files===
When selecting a file you can view the result files by pressing "Get Result Files" if there are available result files. That will create a window where you can search, view and download result files. It is also possible to view result files from multiple assignments at the same time by selecting many assignments of the same type (Only possible for Signal Reader and MCD-Hub tasks).
====Searching result files====
The window will look different depending on what kind of assignment you selected watching. The different windows all share a lot of tools and have the same concept: to search and filter files. In illustration 6 you can see how a MCD-Hub result window looks. This is a great example as this window contains all different tools while all the others can be seen as an MCD-Hub window that does not need and therefore lacks some of the tools. There are some tools that all have and just like when creating a task the common ones are at the top. Below is a description of all tools followed by which assignment window that has them:

===== General search functions =====
[[File:Get Result files.png|thumb|400x400px|Illustration 6: The-MCD-Hub result file window.]]
At the top there are two boxes, labeled "Description" and "Filename", whereby you can search for files based on their description and filename. The "Description" box is disabled so that you can not type in it. When searching by filename it will search for actual result files, the not compiled (i.e. zip) files. Below there are two other sections with two checkboxes. The sections are labeled "From" and "To" and contain dates that can be changed by using the calendar next to the box. The files are filtered so only files between those two dates are shown. The checkboxes are labeled "Measurement Date" and "Upload to Portal" and only one of them can be checked. The checkboxes tell if the files will be filtered by measurement or upload date. There is also a checkbox labeled "Hide downloaded files" which will filter out already downloaded files but this button is disabled if the checkbox "Compline by portal update date" is checked. These tools are the same for all type of assignments and can be seen as marked green in illustration 6.

===== GPX inclusion =====
The checkbox "Include GPX" enables GPX files containing positioning data to be included when downloading result files. That means each downloaded result file will have a corresponding gpx file containing the route of the car when the assignment was executed. Note that the en date for the route is 24 hours after the start since assignments does not always have end dates. ETAS, Softhub, SignalReader and MCD-Hub assignments has this tool and its marked pink in illustration 6.

===== File type filters =====
There are three sections of checkboxes that are framed by a blue line and an outline checkbox labeled "Raw". These sections and the checkbox filter what type of files are shown. The framed sections represent one file type with their own sub-groups. The sections are labeled with what file type they filter. When the outline checkbox in the framed section is checked, it will show you that section's file type. When the respective outline checkbox is not checked, the other checkboxes are disabled as they represent the sub-groups for that file type. The "Raw" checkbox is simpler since it only indicates whether you want to show raw files and lacks sub-groups. As with the other search functions in the WICE portal, leaving all filters empty will result in everything being shown. The section labeled "Text" has three other checkboxes which will show you "Common", "Separate" and "All" text files. Note that not all text files have the subtype "Common" or "Seprate" and can only be shown in "All". The section labeled "MDF" has two other checkboxes which will show you MDF files "With module names" or "Without module names" (i.e. either with or without prefixes in the signal names). The section labeled "Vector" has two other checkboxes which will show you files referring to frames by "Frame ID" or "Frame name". Typically, the MCD-Hub, Softhub and Signal Reader measurement tools generate these file types (but note that Signal Reader does not have the "Raw" option). These tools are marked blue in illustration 6.

===== Compile by upload date =====
The checkbox "Compile by portal upload date" will compile result files into a zip file if they were uploaded at the same time. When the files are compiled some functions that usually work on result files work differently, or do not work at all. As mentioned before, you cannot search for the compiled file since it does not really exist, but is rather created on demand. But when searching with this option turned on, the compiled file will show up if one or more of the files it contains match the search criteria. This search feature is automatically turned on since you are often looking for a specific uploaded file. MCD-Hub, Softhub and Signal Reader has this option and it is marked yellow in illustration 6.

====Handling result files====
When you have selected the result file(s) you want different buttons will be active depending on the file. The buttons are above the column bar and it is where you download, view and convert result files.

"Get file(s)", "Get all files" and "Get log files" will open a dialog to [[Downloading Files|download]] selected files, all files or that dates log files. In the dialog you will get the option to add a description, when downloading result files you can also add plate number and/or VIN to the file name. Note that downloading log files from multiple result files will download only log files 24 after the oldest result files so download log files from result files one result file at a time.

"Save Headers" saves your current view of columns and files and saves it as default. This button has since been replaced by the two binoculars that are described in The Portal User View#The Search Fields Section. We therefore advice you to use the new and improved binoculars as save headers will be removed.

"Plot route" will open a map in your current window. In that map you can see up to 100 cars' registered positions during the last 24 hours or the last 100 registered positions. For more information about this read [[Plot Route Dialog]].

"View log files" will view log files from the selected file´s date. When viewing log files from multiple result files at the same time it will show you log files 24 hours after the oldest result file and not from both dates. you can always change the dates when viewing log files to narrow or widen the amount of files. When viewing log files you can read them by selecting a file and pressing "View file". There is also the option to "Get file(s)", "Save Headers", "Plot route" and "View file" who are all except "View file" described above. "View file" will open the log file in readable format in your current window. You can also filter log files like you filter result files by date, name and if they are downloaded or not. Note that when selecting to view log files from many files it will show log files from the oldest file's date and 24 hours forward.

"View file" will open the file in a readable format in you current window. If the file is compiled by upload date or not readable this button will not be enabled.

"Convert to text" will convert and download selected MDF file(s) to your computer. When doing this you will get a pop-up with the ability to add a description to your download. This is only availible for MDF files and this button can therefore only be found on assignments with MDF files.

=== Preview data ===
"Preview data" will give you a data preview window where you can preview the selected file(s) data. To read more about how to use this window and all its functions read [[Preview data]].

The Portal Administrator View

2018-06-28T13:04:29Z

Richard.wecke: /* Connection */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described [[WCU as WiFi Access Point|here.]]

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
There are two configurations for Canrecorder, one legacy (for WICE versions older than 2.46) and the other for later versions of WICE.
The legacy configuration for the Canrecorder module is shown in Illustration 41.1 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41.1: Legacy configuration options for Canrecorder.|center]]

For later versions there is only one option that is configurable, the debug level. The configuration is shown in illustration 41.2 below.
[[File:CanrecorderModule.png|center|600px|thumb|Illustration 41.2: Current module configuration for Canrecorder.]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

MediaWiki:Sidebar

2018-06-28T13:00:11Z

Richard.wecke:

WCU as WiFi Access Point

2018-06-28T12:56:50Z

Richard.wecke: Created page with "The Connection tab in the WCU configuration {|class = "wikitable" !'''Internet Service Provider (ISP)''' |Which ISP to use when multiple SIM cards..."

[[File:Connection v1.png|The Connection tab in the WCU configuration]]
{|class = "wikitable"
!'''Internet Service Provider (ISP)'''
|Which ISP to use when multiple SIM cards are installed
|-
!'''WICE portal address'''
|The server that the WCU should use for fetching new assignments etc.
|-
!'''DRO Server'''
|The server to connect to when doing a Diagnostic Read-Out.
|}

=== Remote Login ===
[[File:Remotelogin.png|Settings for remote login.]]
{| class = "wikitable"
!'''Enable'''
|To be able to remotely login to the WCU you must first enable the functionality by checking this box.
|-
!'''Server'''
|The remote login proxy server to be used.
|-
!'''Username'''
|Username to be used when doing remote login.
|}

=== WLAN ===
{| class = "wikitable"
!'''Enable'''
|If set, the WCU will try the WLAN connection first when communicating with the portal.
|-
!'''Type of WLAN'''
|Option for configuring the WCU as a WLAN client or as a WLAN Access Point.
|}

==== Client ====
[[File:Wlanandclient.png|Settings for WLAN as Client.]]
{| class = "wikitable"
!'''SSID'''
|The primary name associated with the WLAN that the WCU should connect to.
|-
!'''Passphrase'''
|Password for the WLAN connection.
|-
!'''Security'''
|Option for setting the Security protocol to WPA2 personal or WPA2 PEAP.
|-
!'''WPA2 Personal'''
|Read more about WPA2 [https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access here.]
|-
!'''WPA2 PEAP'''
|Read more about PEAP [https://en.wikipedia.org/wiki/Protected_Extensible_Authentication_Protocol here.]
|-
!'''Identity'''
|The Identity is used in PEAP in order for the authenticator to choose the correct authentication server to process the credentials.
|-
!'''Certificate'''
|Certificate used for network access authentication.
|}

==== Access Point ====
[[File:Wlanandap.png|Settings for WLAN as Access Point.]]
{| class = "wikitable"
!'''SSID'''
|The primary name associated with the WLAN Access Point.
|-
!'''Passphrase'''
|Password for the WLAN AP connection.
|-
!'''Country Code'''
|The country code for the country where the WCU will be acting as a WLAN Access point.
|}

File:Wlanandap.png

2018-06-28T12:25:56Z

Richard.wecke: Settings for WLAN as Access Point

Settings for WLAN as Access Point

File:Wlanandclient.png

2018-06-28T12:25:27Z

Richard.wecke: Settings for WLAN as Client.

Settings for WLAN as Client.

File:Remotelogin.png

2018-06-28T12:24:22Z

Richard.wecke: Settings for remote login.

Settings for remote login.

File:Connection v1.png

2018-06-28T12:22:49Z

Richard.wecke: The connection tab in the WCU configuration.

The connection tab in the WCU configuration.

New in v2.48

2018-06-28T12:19:13Z

Richard.wecke: /* WCU as Wi-fi Access Point */

This page lists new and changed features in version 2.48 of the WICE Portal.

== Strict resource groups ==
Strict resource groups have been added to help manage measurement on large fleets of vehicles with minimum micromanagement.

== WCU as Wi-Fi Access Point ==
A WCU can now be configured to act as a Wi-fi Access Point (see [[WCU as WiFi Access Point|WCU as Wi-Fi Access Point]])

== Stopping assignments ==
Stopping of assignments in the Tasks tab have been reworked to be more intuitive and work with strict resource groups (see [[The Portal User View#Stopping assignments|stopping assignments]]).

== Canrecorder ==
Canrecorder now supports up to 6 CAN buses with CAN frame filters per CAN bus. For a closer look at how to set up a Canrecorder task, see [[The Portal User View#CAN-recorder|The Portal User View]]

== Default CAN channel should now be visible in the interface for IDC, SoH,SWDL and VinReader. ==
Users can now set a default CAN bus (Default CAN channel), on which request from the assignments are sent to. The actual CAN buses are selected from the Configuration. The settings can be found in each respective tool (found in the Modules panel).

== Support for WCU reporting back the status for its configurations ==
The WCU can now report the result of updating both the tool-configuration as well as the WCU-configuration, back to the user. The different statuses for updating are: Ok, Warning or Error. Additional text can be added, shown when hovering the mouse pointer over the status indicator.

== Added functionality to MDF preview/monitor ==
User can now :
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

== Possible to search for empty fields in the Vehicles panel ==
It is now possible to search for empty fields in the Vehicles panel by entering the regular expression "^$". Any field that is a string can be searched this way except for VIN and VCU ID.

== Improved IDC-assignment CAN mapping ==
It is now possible to:
* Map all rows to one CAN bus.
* Select a partial amount of all rows and map them to one CAN bus.

== Resources can now be moved directly between resource groups ==
It is now possible to move resources between resource groups without having to first remove them from the resource group they currently belong to. Users can simply mark the resources they wish to move and press the "Add resource to resource group" button. A dialog will appear informing that resources will be removed from the group they currently belong to. By pressing "OK", the transaction will complete and the resources will be moved to the desired resource group. See [[The Portal Administrator View#Resource Groups|The Administrator Portal View]] for more.

== Support for Video preview ==
To learn more about configuring the Video module and creating Video assignments, see the [[WICE video|page about WICE Video]].

== Support for searching with the AND operator between labels ==
Users can use search expressions containing the operator AND when searching via labels.

== Get the resource group from contained member ==
Users can search out the resource group that a resource belongs to, in the Vehicles panel.

Creating a Task

2018-06-28T08:48:22Z

Richard.wecke: /* Files containing references to sequence files */

<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. Here we will go through how to create tasks of each of the nine different kinds of assignments available (MCD-Hub, Canrecorder, IDC, SoH, Signal Reader, SWDL, ETAS, SoftHub and blue piraT). Note that step 3-6 on MCD-Hub is identical on all assignments so it will not be described to avoid this being repetitive.
[[File:Illustration MCDHub.png|thumb|400x400px|illustration 1: MCD-Hub]]

===MCD-Hub===
MCD-Hub assignments are used to collect data using the MCD-Hub flight recorder. This assignment tab has seven parts (as shown in illustration 1) with one function each that is used as follows:

1. Selecting which MCD-Hub assignment file to use. Press "Bläddra"/"Browse" to bring up the file selection where you select the .hub file to use. The assignment file is typically created using the MCD Tool software.

2. Choose which formats the MCD-Hub result files should be converted to when result files are uploaded to the portal from a WCU.

3. Write a descriptive text for the assignment (optional).

4. Assign owner and the period of validity to the assignment. This is filled automatically and is optionally changed.

5. The "Add schedule" option is under construction, do not use except for special cases.

6. Start searching and selecting target WCUs by pressing add resources at the bottom left of the screen. There you will get a pop up with two boxes, the upper one for searching cars and the bottom one for selected cars. In the top one you can search for WCUs using ten different parameters by writing a value and pressing search or ENTER. To select a WCU you drag it from the top to the bottom box so that it appears in the bottom one.

After you press OK there will be a pop-up telling you "Transfer ok!" if everything went well, otherwise there will be a pop-up dialog showing you an error message.

===CAN-recorder===
[[File:CanrecorderIllust.png|thumb|Illustration 2: Canrecorder]]
Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment has four options described in illustration 2 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.

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

===SoH===
[[File:Illustration SoH.png|thumb|271x271px|Illustration 3: SoH tab]]
A State of Health (SoH) assignment collects specific status information from vechiles. You select which information you want the assignment to collect by filling in one or more of the six boxes shown in illustration 3. In order for SoH data to be correctly interpreted, relevant description files (SDDB/GDS) for the vehicles executing the SoH assignment must have been defined. To add a SDDB/GDS file to a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:
*Mileage
*Voltage
*Read ECU software numbers
*Read ECU DTC:s
*Read OBD-II PIDs
*App Diagnotstic Db Part Num

===Signal Reader===
[[File:Illustration SignalReader.png|thumb|271x271px|Illustration 4.1: Signal reader assignment.]]
Signal Reader is a measurement module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data. Signal Reader performs more or less the same kind of measurements as the MCD-Hub but it has other functions as well. Those other functions are described below and shown in illustration 4.1:

1. You either select an assignment file of .haf format, or choose an assignment blueprint created in the blueprint creator. Your current choice will be displayed in the "Chosen file" field.

2. When you have selected a file and WCU unit(s), the buses defined in the file and on the WCU will be mapped. If they can be automatically mapped a green check 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, 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 follow WCU signals live by selecting "Monitor signals". When selected it will come up two boxes under the task description. In the left one you search for signals and drag them over to the right one where the monitored signals are. You can later se the monitored signals through 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. ECM.EngineSpeed instead of EngineSpeed).

Signal Reader can also act as a signal broker for other software components. Read more about this in [[WICE Signal Broker API]].

==== Files containing references to sequence files ====
[[File:SequenceFileForSignalreader.png|thumb|right|Illustartion 4.2: Sequence files references found in the .haf file]]
If the measurement file contains references to sequence files, you are also required to select these in order to run the assignment. The portal scans the .haf file for such entries and presents this to you, see illustration 4.2. Click the button for each sequence file reference to upload each sequence file needed. Some queries in the sequence file are of functional type, i.e. posed to all ECUs, and in such cases you can select the option of using ''Snapshots'' or ''Extended data''. An example of this can found in illustration 4.2.
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Illustration 4.3: 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 illustration 4.3 we have selected one such sequence file containing functional queries. Here we have checked that we would like to read ''Extended data''. It is also possible to select both ''Snapshots'' and ''Extended data''.
 

===SWDL===
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs.

===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 more recent version of the MCD-Hub measurement system, and a SoftHub task is created much in the same way an MCD-Hub task is.

When creating a SoftHub task, it is identical to a MCD-Hub task except that the file you select must be a .shub file.

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

===Video===
A video task makes it possible to record and monitor live video from one or two cameras attached to a WCU. You can trigger recording of video using either a trigger button or a recorder start event from Signal Reader. You can alson let the video recording start as soon as the WCUs has started. If monitoring of video from a WCU is enabled, a live video stream will be transmitted which can be viewed using a RTP-based video tool, for instance [http://confero.alkit.se Alkit Confero].

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

Creating a Task

2018-06-28T08:23:59Z

Richard.wecke: /* Signal Reader */

<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. Here we will go through how to create tasks of each of the nine different kinds of assignments available (MCD-Hub, Canrecorder, IDC, SoH, Signal Reader, SWDL, ETAS, SoftHub and blue piraT). Note that step 3-6 on MCD-Hub is identical on all assignments so it will not be described to avoid this being repetitive.
[[File:Illustration MCDHub.png|thumb|400x400px|illustration 1: MCD-Hub]]

===MCD-Hub===
MCD-Hub assignments are used to collect data using the MCD-Hub flight recorder. This assignment tab has seven parts (as shown in illustration 1) with one function each that is used as follows:

1. Selecting which MCD-Hub assignment file to use. Press "Bläddra"/"Browse" to bring up the file selection where you select the .hub file to use. The assignment file is typically created using the MCD Tool software.

2. Choose which formats the MCD-Hub result files should be converted to when result files are uploaded to the portal from a WCU.

3. Write a descriptive text for the assignment (optional).

4. Assign owner and the period of validity to the assignment. This is filled automatically and is optionally changed.

5. The "Add schedule" option is under construction, do not use except for special cases.

6. Start searching and selecting target WCUs by pressing add resources at the bottom left of the screen. There you will get a pop up with two boxes, the upper one for searching cars and the bottom one for selected cars. In the top one you can search for WCUs using ten different parameters by writing a value and pressing search or ENTER. To select a WCU you drag it from the top to the bottom box so that it appears in the bottom one.

After you press OK there will be a pop-up telling you "Transfer ok!" if everything went well, otherwise there will be a pop-up dialog showing you an error message.

===CAN-recorder===
[[File:CanrecorderIllust.png|thumb|Illustration 2: Canrecorder]]
Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment has four options described in illustration 2 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.

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

===SoH===
[[File:Illustration SoH.png|thumb|271x271px|Illustration 3: SoH tab]]
A State of Health (SoH) assignment collects specific status information from vechiles. You select which information you want the assignment to collect by filling in one or more of the six boxes shown in illustration 3. In order for SoH data to be correctly interpreted, relevant description files (SDDB/GDS) for the vehicles executing the SoH assignment must have been defined. To add a SDDB/GDS file to a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:
*Mileage
*Voltage
*Read ECU software numbers
*Read ECU DTC:s
*Read OBD-II PIDs
*App Diagnotstic Db Part Num

===Signal Reader===
[[File:Illustration SignalReader.png|thumb|271x271px|Illustration 4.1: Signal reader assignment.]]
Signal Reader is a measurement module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data. Signal Reader performs more or less the same kind of measurements as the MCD-Hub but it has other functions as well. Those other functions are described below and shown in illustration 4.1:

1. You either select an assignment file of .haf format, or choose an assignment blueprint created in the blueprint creator. Your current choice will be displayed in the "Chosen file" field.

2. When you have selected a file and WCU unit(s), the buses defined in the file and on the WCU will be mapped. If they can be automatically mapped a green check 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, 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 follow WCU signals live by selecting "Monitor signals". When selected it will come up two boxes under the task description. In the left one you search for signals and drag them over to the right one where the monitored signals are. You can later se the monitored signals through 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. ECM.EngineSpeed instead of EngineSpeed).

Signal Reader can also act as a signal broker for other software components. Read more about this in [[WICE Signal Broker API]].

==== Files containing references to sequence files ====
[[File:SequenceFileForSignalreader.png|thumb|right|Illustartion 4.2: Sequence files references found in the .haf file]]
When the measurement file contains sequence files the user must help by selecting the local which sequence files that are needed in order to run the assignment. The portal scans the .haf file for such entries and presents this to the user, see to the right. Click the button for each sequence file reference to upload each sequence file needed. Some queries in the sequence file are of functional type, i.e. posed to all ECUs, and in such cases you have the option of doing it using snapshots or extended data. An example of this can found in illustration 4.2.
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Illustration 4.3: 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 illustration 4.3 we have selected one such sequence file containing functional queries. We have here checked that we would like to read extended data as well. One could also check both options.
 

===SWDL===
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs.

===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 more recent version of the MCD-Hub measurement system, and a SoftHub task is created much in the same way an MCD-Hub task is.

When creating a SoftHub task, it is identical to a MCD-Hub task except that the file you select must be a .shub file.

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

===Video===
A video task makes it possible to record and monitor live video from one or two cameras attached to a WCU. You can trigger recording of video using either a trigger button or a recorder start event from Signal Reader. You can alson let the video recording start as soon as the WCUs has started. If monitoring of video from a WCU is enabled, a live video stream will be transmitted which can be viewed using a RTP-based video tool, for instance [http://confero.alkit.se Alkit Confero].

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

File:SequenceFilesForSignalreaderWithFunctionalQuery.png

2018-06-28T08:13:32Z

Richard.wecke: Sequence file with functional query

Sequence file with functional query

File:SequenceFileForSignalreader.png

2018-06-28T08:12:37Z

Richard.wecke: Sequence files references found in the .haf file.

Sequence files references found in the .haf file.

Creating a Task

2018-06-28T08:08:42Z

Richard.wecke: /* Signal Reader */

<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. Here we will go through how to create tasks of each of the nine different kinds of assignments available (MCD-Hub, Canrecorder, IDC, SoH, Signal Reader, SWDL, ETAS, SoftHub and blue piraT). Note that step 3-6 on MCD-Hub is identical on all assignments so it will not be described to avoid this being repetitive.
[[File:Illustration MCDHub.png|thumb|400x400px|illustration 1: MCD-Hub]]

===MCD-Hub===
MCD-Hub assignments are used to collect data using the MCD-Hub flight recorder. This assignment tab has seven parts (as shown in illustration 1) with one function each that is used as follows:

1. Selecting which MCD-Hub assignment file to use. Press "Bläddra"/"Browse" to bring up the file selection where you select the .hub file to use. The assignment file is typically created using the MCD Tool software.

2. Choose which formats the MCD-Hub result files should be converted to when result files are uploaded to the portal from a WCU.

3. Write a descriptive text for the assignment (optional).

4. Assign owner and the period of validity to the assignment. This is filled automatically and is optionally changed.

5. The "Add schedule" option is under construction, do not use except for special cases.

6. Start searching and selecting target WCUs by pressing add resources at the bottom left of the screen. There you will get a pop up with two boxes, the upper one for searching cars and the bottom one for selected cars. In the top one you can search for WCUs using ten different parameters by writing a value and pressing search or ENTER. To select a WCU you drag it from the top to the bottom box so that it appears in the bottom one.

After you press OK there will be a pop-up telling you "Transfer ok!" if everything went well, otherwise there will be a pop-up dialog showing you an error message.

===CAN-recorder===
[[File:CanrecorderIllust.png|thumb|Illustration 2: Canrecorder]]
Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment has four options described in illustration 2 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.

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

===SoH===
[[File:Illustration SoH.png|thumb|271x271px|Illustration 3: SoH tab]]
A State of Health (SoH) assignment collects specific status information from vechiles. You select which information you want the assignment to collect by filling in one or more of the six boxes shown in illustration 3. In order for SoH data to be correctly interpreted, relevant description files (SDDB/GDS) for the vehicles executing the SoH assignment must have been defined. To add a SDDB/GDS file to a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:
*Mileage
*Voltage
*Read ECU software numbers
*Read ECU DTC:s
*Read OBD-II PIDs
*App Diagnotstic Db Part Num

===Signal Reader===
[[File:Illustration SignalReader.png|thumb|271x271px|Illustration 4: Signal reader assignment.]]
Signal Reader is a measurement module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data. Signal Reader performs more or less the same kind of measurements as the MCD-Hub but it has other functions as well. Those other functions are described below and shown in illustration 4:

1. You either select an assignment file of .haf format, or choose an assignment blueprint created in the blueprint creator. Your current choice will be displayed in the "Chosen file" field.

2. When you have selected a file and WCU unit(s), the buses defined in the file and on the WCU will be mapped. If they can be automatically mapped a green check 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, 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 follow WCU signals live by selecting "Monitor signals". When selected it will come up two boxes under the task description. In the left one you search for signals and drag them over to the right one where the monitored signals are. You can later se the monitored signals through 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. ECM.EngineSpeed instead of EngineSpeed).

Signal Reader can also act as a signal broker for other software components. Read more about this in [[WICE Signal Broker API]].

===SWDL===
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs.

===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 more recent version of the MCD-Hub measurement system, and a SoftHub task is created much in the same way an MCD-Hub task is.

When creating a SoftHub task, it is identical to a MCD-Hub task except that the file you select must be a .shub file.

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

===Video===
A video task makes it possible to record and monitor live video from one or two cameras attached to a WCU. You can trigger recording of video using either a trigger button or a recorder start event from Signal Reader. You can alson let the video recording start as soon as the WCUs has started. If monitoring of video from a WCU is enabled, a live video stream will be transmitted which can be viewed using a RTP-based video tool, for instance [http://confero.alkit.se Alkit Confero].

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

Creating a Task

2018-06-27T14:44:16Z

Richard.wecke: /* Signal Reader */

<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. Here we will go through how to create tasks of each of the nine different kinds of assignments available (MCD-Hub, Canrecorder, IDC, SoH, Signal Reader, SWDL, ETAS, SoftHub and blue piraT). Note that step 3-6 on MCD-Hub is identical on all assignments so it will not be described to avoid this being repetitive.
[[File:Illustration MCDHub.png|thumb|400x400px|illustration 1: MCD-Hub]]

===MCD-Hub===
MCD-Hub assignments are used to collect data using the MCD-Hub flight recorder. This assignment tab has seven parts (as shown in illustration 1) with one function each that is used as follows:

1. Selecting which MCD-Hub assignment file to use. Press "Bläddra"/"Browse" to bring up the file selection where you select the .hub file to use. The assignment file is typically created using the MCD Tool software.

2. Choose which formats the MCD-Hub result files should be converted to when result files are uploaded to the portal from a WCU.

3. Write a descriptive text for the assignment (optional).

4. Assign owner and the period of validity to the assignment. This is filled automatically and is optionally changed.

5. The "Add schedule" option is under construction, do not use except for special cases.

6. Start searching and selecting target WCUs by pressing add resources at the bottom left of the screen. There you will get a pop up with two boxes, the upper one for searching cars and the bottom one for selected cars. In the top one you can search for WCUs using ten different parameters by writing a value and pressing search or ENTER. To select a WCU you drag it from the top to the bottom box so that it appears in the bottom one.

After you press OK there will be a pop-up telling you "Transfer ok!" if everything went well, otherwise there will be a pop-up dialog showing you an error message.

===CAN-recorder===
[[File:CanrecorderIllust.png|thumb|Illustration 2: Canrecorder]]
Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment has four options described in illustration 2 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.

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

===SoH===
[[File:Illustration SoH.png|thumb|271x271px|Illustration 3: SoH tab]]
A State of Health (SoH) assignment collects specific status information from vechiles. You select which information you want the assignment to collect by filling in one or more of the six boxes shown in illustration 3. In order for SoH data to be correctly interpreted, relevant description files (SDDB/GDS) for the vehicles executing the SoH assignment must have been defined. To add a SDDB/GDS file to a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:
*Mileage
*Voltage
*Read ECU software numbers
*Read ECU DTC:s
*Read OBD-II PIDs
*App Diagnotstic Db Part Num

===Signal Reader===
see [[Signalreader|Signalreader]]
[[File:Illustration SignalReader.png|thumb|271x271px|Illustration 4: Signal reader assignment.]]
Signal Reader is a measurement module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data. Signal Reader performs more or less the same kind of measurements as the MCD-Hub but it has other functions as well. Those other functions are described below and shown in illustration 4:

1. You either select an assignment file of .haf format, or choose an assignment blueprint created in the blueprint creator. Your current choice will be displayed in the "Chosen file" field.

2. When you have selected a file and WCU unit(s), the buses defined in the file and on the WCU will be mapped. If they can be automatically mapped a green check 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, 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 follow WCU signals live by selecting "Monitor signals". When selected it will come up two boxes under the task description. In the left one you search for signals and drag them over to the right one where the monitored signals are. You can later se the monitored signals through 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. ECM.EngineSpeed instead of EngineSpeed).

Signal Reader can also act as a signal broker for other software components. Read more about this in [[WICE Signal Broker API]].

===SWDL===
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs.

===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 more recent version of the MCD-Hub measurement system, and a SoftHub task is created much in the same way an MCD-Hub task is.

When creating a SoftHub task, it is identical to a MCD-Hub task except that the file you select must be a .shub file.

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

===Video===
A video task makes it possible to record and monitor live video from one or two cameras attached to a WCU. You can trigger recording of video using either a trigger button or a recorder start event from Signal Reader. You can alson let the video recording start as soon as the WCUs has started. If monitoring of video from a WCU is enabled, a live video stream will be transmitted which can be viewed using a RTP-based video tool, for instance [http://confero.alkit.se Alkit Confero].

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

The Portal Administrator View

2018-06-27T14:34:01Z

Richard.wecke: /* Configure the Canrecorder Module */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
There are two configurations for Canrecorder, one legacy (for WICE versions older than 2.46) and the other for later versions of WICE.
The legacy configuration for the Canrecorder module is shown in Illustration 41.1 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41.1: Legacy configuration options for Canrecorder.|center]]

For later versions there is only one option that is configurable, the debug level. The configuration is shown in illustration 41.2 below.
[[File:CanrecorderModule.png|center|600px|thumb|Illustration 41.2: Current module configuration for Canrecorder.]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-27T14:32:34Z

Richard.wecke: /* Configure the Canrecorder Module */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
Therer are two configurations for Canrecorder, one legacy (for WICE versions older than 2.46) and the other for later versions of WICE.
The legacy configuration for the Canrecorder module is shown in Illustration 41.1 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41.1: Legacy configuration options for Canrecorder.|center]]

For later versions there is only one option that is configurable, the debug level. The configuration is shown in illustration 41.2 below.
[[File:CanrecorderModule.png|center|600px|thumb|Illustration 41.2: Current module configuration for Canrecorder.]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

File:CanrecorderModule.png

2018-06-27T14:15:54Z

Richard.wecke: Module configuration for Canrecorder

Module configuration for Canrecorder

Strict resource group

2018-06-27T13:54:46Z

Richard.wecke:

A strict resource group is a type of resource group. Strict resource groups are generally ment to be used during the following conditions:

*Large amount of vehicles are to be measured in exactly the same way.
*The same WCU platform, modules, and WCU software version is installed in all vehicles.
*No deviations in WCU or Module configurations.

This allows for easy management of measurements in large fleets of vehicles at a cost of freedom in micromanagement. The strict resource groups system is built to be robust, and minimize the risk of usage error causing the measurements not to start.

[[File:Lock.png|25px|left|]] A blue lock icon is used around the portal to indicate that a resource or resource group is strict.

'''Note''': It is currently only possible to run Signalreader and SoH assignments on a strict resource group. This is intended to be expanded to more assignment types in coming versions of WICE.

Strict resource groups come with a number of features and limitations. A summary is provided here, with more in depth documentation below:

*All vehicles will automatically receive the same measurement assignments.
*All WCUs must have the same platform- and sub-type.
*All WCUs and modules will automatically receive the same configurations.
*All cars must have a SDDB file connected.

'''Note''': If you want to temporarily change an individual WCU for some reason, you can remove it from the resource group at any time to make it editable. Don’t worry, the WCU will keep all measure assignments and configurations it had in the group.

'''Note''': WICE does '''not''' support physically moving WCUs from one car to another while in a strict resource group. If you wish to do this, please remove the resource from the group, stop all potential assignments (and wait for the WCU to report them “Stopped”), physically move the WCU, wait for the WCU to acknowledge the new car in the portal, and then add it to the resource group again.

=== Measure assignment ===
On of the main features of strict resource groups is the automatic application of measure assignments to resources added. Since all resources in the group are forced to use the same platform type and configurations, the system can assure the assignment can run given that the hardware is in order.

=== Platform type ===
Strict resource groups need all WCUs in it to be of the same platform- and subtype. When a strict resource group is created, you must select the platform- and subtype. Only WCUs matching these types can be added to this resource group.

It is currently not possible to change the platform type of a strict resource group. If an administrator makes the group non-strict, the platform type can be changed in the configuration, and the group can be made strict again.

=== WCU and Module configuration ===
Strict resource groups atomically inherit WCU configuration and all Module configurations from the resource group. Unlike normal resource groups, there is no option to deviate from the configurations of the strict resource group.

These are applied automatically when the resource is added to the resource group.

=== Assignment Status for Task on Strict Resource Group ===
The status on a task created for a strict resource group will reflect the status of that task on all of the members of the resource group. See the table below for how the status of the strict resource group’s task is determined:
{| class = "wikitable"
!'''Status'''
|'''Explanation'''
|-
!Pending
|No child task running, but at least one is pending
|-
!Running
|All child tasks are running
|-
!Partially Running
|At least one child task is running
|-
!Warning
|No child task running, pending or error, but at least one is warning
|-
!Error
|No child task running or pending, but at least one is error
|-
!Stop Pending
|No child task running, pending, warning or error, but at least one is stop pending
|-
!Stopped
|All child tasks stopped
|}

Icons will display to indicate if a status pending or partially running also contains an error or warning status.

Strict resource group

2018-06-27T13:45:13Z

Richard.wecke: Created page with "A strict resource group is a type of resource group. Strict resource groups are generally ment to be used during the following conditions: *Large amount of vehicles are t..."

File:Lock.png

2018-06-27T13:26:58Z

Richard.wecke: Lock icon for strict resource groups.

Lock icon for strict resource groups.

Vehicles

2018-06-27T12:34:43Z

Richard.wecke: /* Resource Groups */

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in Illustration 26. At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.
[[File:Illustration26.png|none|thumb|700x700px|Illustration 26: The vehicles tab]]
The number of possible columns to show is quite large (24). The columns shown below are in
default order. You will have to account for any changes you have made yourself. The columns
are:

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

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

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

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

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

[[File:Illustration27.png|none|left|frame|Illustration 27: An example vehicle map view.]]

To the right of the map view is a list of all the vehicles. Each vehicle is labeled with the license plate number and if you click on a vehicle entry on the right, an information pop-up will appear for the vehicle. If you click on the marker of a vehicle, a new tab is opened in the browser that shows what Google Maps has to offer on that position.
Also, just moving the mouse pointer over a marker will make the pop-up appear.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Vehicles

2018-06-27T12:34:23Z

Richard.wecke: /* Resource Groups */

<includeonly>=Vehicles Tab=</includeonly>
This view is used to handle the various vehicles that are assigned to you. A figure of this view
is presented below in Illustration 26. At the top, the red section, is a search area where you
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your
criteria a row count is presented in the upper right area to show how many potential matches
there are. The entries are also fetched as you type but only as many rows as fit your current
view are fetched. As you scroll down more results will be fetched.
[[File:Illustration26.png|none|thumb|700x700px|Illustration 26: The vehicles tab]]
The number of possible columns to show is quite large (24). The columns shown below are in
default order. You will have to account for any changes you have made yourself. The columns
are:

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

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

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

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

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

[[File:Illustration27.png|none|left|frame|Illustration 27: An example vehicle map view.]]

To the right of the map view is a list of all the vehicles. Each vehicle is labeled with the license plate number and if you click on a vehicle entry on the right, an information pop-up will appear for the vehicle. If you click on the marker of a vehicle, a new tab is opened in the browser that shows what Google Maps has to offer on that position.
Also, just moving the mouse pointer over a marker will make the pop-up appear.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Stopping assignments

2018-06-27T11:04:01Z

Richard.wecke: /* Force Stop Assignment */

<includeonly>= Stopping assignments=</includeonly>
The tasks tab provides options to stop measure assignments in multiple ways. These are explained below.

Assignments can assume multiple states
{| class="wikitable"
!Pending
|The assignment is waiting for the WCU to download it.
|-
!Running
|The WCU has downloaded the assignment and it has started.
|-
!Warning
|The assignment is running on the WCU, but has reported warnings.
|-
!Error
|The WCU has attempted to start the assignment, but has reported back major problems (that may have prevented it to run).
|-
!Stop pending
|The WCU still has the assignment applied, but will stop it next time it connects to the portal.
|-
!Stopped
|The WCU has stopped running the assignment.
|}

=== Resume assignment ===

Used to undo the stopping of an assignment. This is only usable on ''Stop Pending'' assignments, and reapplies the assignment so that the WCU will continue running it. If there is another assignment of the same type currently in ''Pending'' for that WCU, that assignment is changed to ''Stopped'', and will never be downloaded by the WCU.

=== Cancel Assignment ===
Used to undo the application of a new assignment. Only useable on ''Pending'' assignments. The assignment is instantly ''Stopped'' and if there is an assignment of the same type currently ''Stop Pending'' it reapplies that assignment and changes the status back to ''Running''.

=== Stop Assignment ===
Stops the assignment without replacing it, making the WCU not run anything of that assignment type. Useable on ''Pending'', ''Running'', ''Warning'', and ''Error''. Pending assignments instantly enter a ''Stopped'' state while giving the WCU a stop command. ''Running'', ''Warning'', and ''Error'' assignments enter a ''Stop Pending'' state, waiting for the WCU to report it has stopped before changing state to ''Stopped''.

=== Force Stop Assignment ===
Force stopping an assignment is an Admin feature meant for WCUs which have been physically disconnected by an operator while having an active assignment. In this situation the WCU will not report to the portal that it has actually stopped the assignment (since it will not turn on). In this case, this feature can be used to place the assignment in ''Stopped'' for tracking purposes. This can only be used on ''Stop Pending'' assignment. If you wish to force stop a running/warning/error assignment, you need to stop it first (using Stop Assignment).

'''Note''' that this will not affect the actual WCU in any way.

=== Stopping assignments and strict resource groups ===
You can use these features on [[Strict resource group|strict resource groups]] to stop all assignments of that type running on the WCUs in that group. 
'''Stop Assignment''' will place all the assignments of that type in either ''Stop Pending'' or ''Stopped'' based on their status (see Stop Assignment). 
'''Force Stop Assignment''' can be used used on strict resource groups with status ''Stop Pending'' to force every WCU in the resource group to enter ''Stopped'' state (see Force Stop Assignment).

'''Note''' that '''Resume Assignment''' and '''Cancel Assignment''' can not be used on '''strict''' resource groups.

New in v2.48

2018-06-27T11:02:58Z

Richard.wecke: /* Stopping assignments */

This page lists new and changed features in version 2.48 of the WICE Portal.

== Strict resource groups ==
Strict resource groups have been added to help manage measurement on large fleets of vehicles with minimum micromanagement.

== WCU as Wi-fi Access Point ==
A WCU can now be configured to act as a Wi-fi Access Point

== Stopping assignments ==
Stopping of assignments in the Tasks tab have been reworked to be more intuitive and work with strict resource groups (see [[The Portal User View#Stopping assignments|stopping assignments]]).

== Canrecorder ==
Canrecorder now supports up to 6 CAN buses with CAN frame filters per CAN bus. For a closer look at how to set up a Canrecorder task, see [[The Portal User View#CAN-recorder|The Portal User View]]

== Default CAN channel should now be visible in the interface for IDC, SoH,SWDL and VinReader. ==
Users can now set a default CAN bus (Default CAN channel), on which request from the assignments are sent to. The actual CAN buses are selected from the Configuration. The settings can be found in each respective tool (found in the Modules panel).

== Support for WCU reporting back the status for its configurations ==
The WCU can now report the result of updating both the tool-configuration as well as the WCU-configuration, back to the user. The different statuses for updating are: Ok, Warning or Error. Additional text can be added, shown when hovering the mouse pointer over the status indicator.

== Added functionality to MDF preview/monitor ==
User can now :
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

== Possible to search for empty fields in the Vehicles panel ==
It is now possible to search for empty fields in the Vehicles panel by entering the regular expression "^$". Any field that is a string can be searched this way except for VIN and VCU ID.

== Improved IDC-assignment CAN mapping ==
It is now possible to:
* Map all rows to one CAN bus.
* Select a partial amount of all rows and map them to one CAN bus.

== Resources can now be moved directly between resource groups ==
It is now possible to move resources between resource groups without having to first remove them from the resource group they currently belong to. Users can simply mark the resources they wish to move and press the "Add resource to resource group" button. A dialog will appear informing that resources will be removed from the group they currently belong to. By pressing "OK", the transaction will complete and the resources will be moved to the desired resource group. See [[The Portal Administrator View#Resource Groups|The Administrator Portal View]] for more.

== Support for Video preview ==
To learn more about configuring the Video module and creating Video assignments, see the [[WICE video|page about WICE Video]].

== Support for searching with the AND operator between labels ==
Users can use search expressions containing the operator AND when searching via labels.

== Get the resource group from contained member ==
Users can search out the resource group that a resource belongs to, in the Vehicles panel.

Stopping assignments

2018-06-27T11:01:47Z

Richard.wecke:

<includeonly>= Stopping assignments=</includeonly>
The tasks tab provides options to stop measure assignments in multiple ways. These are explained below.

Assignments can assume multiple states
{| class="wikitable"
!Pending
|The assignment is waiting for the WCU to download it.
|-
!Running
|The WCU has downloaded the assignment and it has started.
|-
!Warning
|The assignment is running on the WCU, but has reported warnings.
|-
!Error
|The WCU has attempted to start the assignment, but has reported back major problems (that may have prevented it to run).
|-
!Stop pending
|The WCU still has the assignment applied, but will stop it next time it connects to the portal.
|-
!Stopped
|The WCU has stopped running the assignment.
|}

=== Resume assignment ===

Used to undo the stopping of an assignment. This is only usable on ''Stop Pending'' assignments, and reapplies the assignment so that the WCU will continue running it. If there is another assignment of the same type currently in ''Pending'' for that WCU, that assignment is changed to ''Stopped'', and will never be downloaded by the WCU.

=== Cancel Assignment ===
Used to undo the application of a new assignment. Only useable on ''Pending'' assignments. The assignment is instantly ''Stopped'' and if there is an assignment of the same type currently ''Stop Pending'' it reapplies that assignment and changes the status back to ''Running''.

=== Stop Assignment ===
Stops the assignment without replacing it, making the WCU not run anything of that assignment type. Useable on ''Pending'', ''Running'', ''Warning'', and ''Error''. Pending assignments instantly enter a ''Stopped'' state while giving the WCU a stop command. ''Running'', ''Warning'', and ''Error'' assignments enter a ''Stop Pending'' state, waiting for the WCU to report it has stopped before changing state to ''Stopped''.

=== Force Stop Assignment ===
Force stopping an assignment is an admin feature meant for WCUs which have been physically disconnected by an operator while having an active assignment. In this situation the WCU will not report to the portal that it has actually stopped the assignment (since it will not turn on). In this case, this feature can be used to place the assignment in ''Stopped'' for tracking purposes. This can only be used on ''Stop Pending'' assignment. If you wish to force stop a running/warning/error assignment, you need to stop it first (using Stop Assignment).

'''Note''' that this will not affect the actual WCU in any way.

=== Stopping assignments and strict resource groups ===
You can use these features on [[Strict resource group|strict resource groups]] to stop all assignments of that type running on the WCUs in that group. 
'''Stop Assignment''' will place all the assignments of that type in either ''Stop Pending'' or ''Stopped'' based on their status (see Stop Assignment). 
'''Force Stop Assignment''' can be used used on strict resource groups with status ''Stop Pending'' to force every WCU in the resource group to enter ''Stopped'' state (see Force Stop Assignment).

'''Note''' that '''Resume Assignment''' and '''Cancel Assignment''' can not be used on '''strict''' resource groups.

The Portal User View

2018-06-27T11:01:14Z

Richard.wecke:

This section will comprehensively explain all panels, dialogs and functionalities of the WICE portal, from a user perspective. Section 3.1 will describe the meaning of the top level panels. In section 3 through 5 each top level panel will be described in detail.

 
{{:Login}}

==Top level tabs==
On the top level there are four different tabs to choose from. From left to right they are:
#'''Tasks''' Manage your tasks, search among tasks and create new tasks.
#'''Search''' In this tab you search and download result files.
#'''Vehicles''' Manage your vehicles. As vehicles belong to users of the system, you need to assign a vehicle to yourself before you initiate tasks running on it. You can also deassign vehicles when you are finished with them.
#'''Administration''' In this tab you can administer your name, email-address, password and a few other things.

With these three tabs you can do all the work that is needed to start, stop and handle data to and from vehicles. A figure of the tabs is presented in Illustration 5 below.
[[File:Illustration11 v240.png|frame|left|Illustration 5: The four tabs shown to a user.]]

 
{{:Tasks Tab}}
 
{{:Creating a Task}}
 
{{:Stopping assignments}}
 
{{:Search Tab}}
 

{{:Vehicles}}

Stopping assignments

2018-06-27T10:59:43Z

Richard.wecke:

<includeonly>= Stopping assignments=</includeonly>
The tasks tab provides options to stop measure assignments in multiple ways. These are explained below.

Assignments can assume multiple states
{| class="wikitable"
!Pending
|The assignment is waiting for the WCU to download it.
|-
!Running
|The WCU has downloaded the assignment and it has started.
|-
!Warning
|The assignment is running on the WCU, but has reported warnings.
|-
!Error
|The WCU has attempted to start the assignment, but has reported back major problems (that may have prevented it to run).
|-
!Stop pending
|The WCU still has the assignment applied, but will stop it next time it connects to the portal.
|-
!Stopped
|The WCU has stopped running the assignment.
|}

=== Resume assignment ===

Used to undo the stopping of an assignment. This is only usable on ''Stop Pending'' assignments, and reapplies the assignment so that the WCU will continue running it. If there is another assignment of the same type currently in ''Pending'' for that WCU, that assignment is changed to ''Stopped'', and will never be downloaded by the WCU.

=== Cancel Assignment ===
Used to undo the application of a new assignment. Only useable on ''Pending'' assignments. The assignment is instantly ''Stopped'' and if there is an assignment of the same type currently ''Stop Pending'' it reapplies that assignment and changes the status back to ''Running''.

=== Stop Assignment ===
Stops the assignment without replacing it, making the WCU not run anything of that assignment type. Useable on ''Pending'', ''Running'', ''Warning'', and ''Error''. Pending assignments instantly enter a ''Stopped'' state while giving the WCU a stop command. ''Running'', ''Warning'', and ''Error'' assignments enter a ''Stop Pending'' state, waiting for the WCU to report it has stopped before changing state to ''Stopped''.

=== Force Stop Assignment ===
Force stopping an assignment is an admin feature meant for WCUs which have been physically disconnected by an operator while having an active assignment. In this situation the WCU will not report to the portal that it has actually stopped the assignment (since it will not turn on). In this case, this feature can be used to place the assignment in ''Stopped'' for tracking purposes. This can only be used on ''Stop Pending'' assignment. If you wish to force stop a running/warning/error assignment, you need to stop it first (using Stop Assignment).

'''Note''' that this will not affect the actual WCU in any way.

=== Stopping assignments and strict resource groups ===
You can use these features on [[Strict resource group|strict resource groups]] to stop all assignments of that type running on the WCUs in that group. 
'''Stop Assignment''' will place all the assignments of that type in either ''Stop Pending'' or ''Stopped'' based on their status (see Stop Assignment). 
'''Force Stop Assignment''' can be used used on strict resource groups with status ''Stop Pending'' to force every WCU in the resource group to enter ''Stopped'' state (see Force Stop Assignment).

'''Note''' that Resume Assignment and Cancel Assignment can not be used on '''strict''' resource groups.

Stopping assignments

2018-06-27T10:57:35Z

Richard.wecke: Created page with " The tasks tab provides options to stop measure assignments in multiple ways. These are explained below. Assignments can assume multiple states {| class="wikitable" !Pendin..."

The tasks tab provides options to stop measure assignments in multiple ways. These are explained below.

Assignments can assume multiple states
{| class="wikitable"
!Pending
|The assignment is waiting for the WCU to download it.
|-
!Running
|The WCU has downloaded the assignment and it has started.
|-
!Warning
|The assignment is running on the WCU, but has reported warnings.
|-
!Error
|The WCU has attempted to start the assignment, but has reported back major problems (that may have prevented it to run).
|-
!Stop pending
|The WCU still has the assignment applied, but will stop it next time it connects to the portal.
|-
!Stopped
|The WCU has stopped running the assignment.
|}

=== Resume assignment ===

Used to undo the stopping of an assignment. This is only usable on ''Stop Pending'' assignments, and reapplies the assignment so that the WCU will continue running it. If there is another assignment of the same type currently in ''Pending'' for that WCU, that assignment is changed to ''Stopped'', and will never be downloaded by the WCU.

=== Cancel Assignment ===
Used to undo the application of a new assignment. Only useable on ''Pending'' assignments. The assignment is instantly ''Stopped'' and if there is an assignment of the same type currently ''Stop Pending'' it reapplies that assignment and changes the status back to ''Running''.

=== Stop Assignment ===
Stops the assignment without replacing it, making the WCU not run anything of that assignment type. Useable on ''Pending'', ''Running'', ''Warning'', and ''Error''. Pending assignments instantly enter a ''Stopped'' state while giving the WCU a stop command. ''Running'', ''Warning'', and ''Error'' assignments enter a ''Stop Pending'' state, waiting for the WCU to report it has stopped before changing state to ''Stopped''.

=== Force Stop Assignment ===
Force stopping an assignment is an admin feature meant for WCUs which have been physically disconnected by an operator while having an active assignment. In this situation the WCU will not report to the portal that it has actually stopped the assignment (since it will not turn on). In this case, this feature can be used to place the assignment in ''Stopped'' for tracking purposes. This can only be used on ''Stop Pending'' assignment. If you wish to force stop a running/warning/error assignment, you need to stop it first (using Stop Assignment).

'''Note''' that this will not affect the actual WCU in any way.

=== Stopping assignments and strict resource groups ===
You can use these features on [[Strict resource group|strict resource groups]] to stop all assignments of that type running on the WCUs in that group. 
'''Stop Assignment''' will place all the assignments of that type in either ''Stop Pending'' or ''Stopped'' based on their status (see Stop Assignment). 
'''Force Stop Assignment''' can be used used on strict resource groups with status ''Stop Pending'' to force every WCU in the resource group to enter ''Stopped'' state (see Force Stop Assignment).

'''Note''' that Resume Assignment and Cancel Assignment can not be used on '''strict''' resource groups.

New in v2.48

2018-06-27T10:25:45Z

Richard.wecke: /* Stopping assignments */

This page lists new and changed features in version 2.48 of the WICE Portal.

== Strict resource groups ==
Strict resource groups have been added to help manage measurement on large fleets of vehicles with minimum micromanagement.

== WCU as Wi-fi Access Point ==
A WCU can now be configured to act as a Wi-fi Access Point

== Stopping assignments ==
Stopping of assignments in the Tasks tab have been reworked to be more intuitive and work with strict resource groups (see [[Stopping assignments|stopping assignments]]).

== Canrecorder ==
Canrecorder now supports up to 6 CAN buses with CAN frame filters per CAN bus. For a closer look at how to set up a Canrecorder task, see [[The Portal User View#CAN-recorder|The Portal User View]]

== Default CAN channel should now be visible in the interface for IDC, SoH,SWDL and VinReader. ==
Users can now set a default CAN bus (Default CAN channel), on which request from the assignments are sent to. The actual CAN buses are selected from the Configuration. The settings can be found in each respective tool (found in the Modules panel).

== Support for WCU reporting back the status for its configurations ==
The WCU can now report the result of updating both the tool-configuration as well as the WCU-configuration, back to the user. The different statuses for updating are: Ok, Warning or Error. Additional text can be added, shown when hovering the mouse pointer over the status indicator.

== Added functionality to MDF preview/monitor ==
User can now :
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

== Possible to search for empty fields in the Vehicles panel ==
It is now possible to search for empty fields in the Vehicles panel by entering the regular expression "^$". Any field that is a string can be searched this way except for VIN and VCU ID.

== Improved IDC-assignment CAN mapping ==
It is now possible to:
* Map all rows to one CAN bus.
* Select a partial amount of all rows and map them to one CAN bus.

== Resources can now be moved directly between resource groups ==
It is now possible to move resources between resource groups without having to first remove them from the resource group they currently belong to. Users can simply mark the resources they wish to move and press the "Add resource to resource group" button. A dialog will appear informing that resources will be removed from the group they currently belong to. By pressing "OK", the transaction will complete and the resources will be moved to the desired resource group. See [[The Portal Administrator View#Resource Groups|The Administrator Portal View]] for more.

== Support for Video preview ==
To learn more about configuring the Video module and creating Video assignments, see the [[WICE video|page about WICE Video]].

== Support for searching with the AND operator between labels ==
Users can use search expressions containing the operator AND when searching via labels.

== Get the resource group from contained member ==
Users can search out the resource group that a resource belongs to, in the Vehicles panel.

Tasks Tab

2018-06-27T08:22:03Z

Richard.wecke: /* The Search Fields Section */

<includeonly>= Tasks Tab=</includeonly>
<div class="keywords"> Regexp, regex, reg ex, regual expression </div>
[[File:Illustration14.png|thumb|The search panel for finding tasks.]]
In the Tasks tab you can search for tasks, view and manage their assignments, see the log files, access result data files, and much more.

==The Search Fields Section==
The search field section consists of different columns where most have a field where you can insert search criteria to find active tasks. As an example you have the label “Task ID:” which searches the field for task IDs matching your search criteria. When searching for tasks you can fill in one or more columns where the different search criteria will be treated with a logical AND between each other.

There are many different columns: in some you can fill in a search criteria and some you can not. Below is a table with all the columns followed by a short description. Note that the columns with a star are the ones where you can enter a search criteria to filter results.
{| class="wikitable"
!Task ID*
|The nummeric Task ID.
|-
!Assignment*
|The assignment name.
|-
!Type*
|Different options for assignment types where one or more can be selected.
|-
!WCU ID*
|The WCU's ID and also the column where you see the WCU's label.
|-
!Upload size
|The upload size of all the assignment's uploads given in Kbytes.
|-
!Plate number*
|The car's plate number.
|-
!Status*
|Different options for assignment statuses where one or more can be selected.
|-
!Last log
|When the last log file was transferred to the portal.
|-
!Last upload
|Date of the assignments's last upload.
|-
!VIN*
|The car's Vehicle Identification Number.
|-
!Proto number*
|The proto number.
|-
!Project*
|The project ID.
|-
!TSU*
|The TSU ID.
|-
!Car comment*
|The car's comment/description.
|-
!Series*
|The series attribute.
|-
!Message*
|The assignment's status message.
|-
!WCU name*
|The name of the WCU.
|-
!Task owner
|The current owner of the task.
|-
!Expire date
|The date the assignment will expire.
|-
!Task creator
|The original creator of the task.
|-
!Creation date
|The creation date of the assignment.
|-
!Resource group*
|The resource group the WCU is part of.
|}
In each searchable column you can use regular expressions for your searches. To designate an "all" search you enter a period (".") for that particular field or leave it empty if another field is already filled in. All searches are treated with the letters as wild-cards. An example is if you intend to search for tasks containing the word “bear” simply enter “bear” in the text field. Now, if there are tasks with the names “bear”, “polar bear”and “unbearable” all of these will match as they contain the word “bear” somewhere.

To search for a range of WCUs, let's say the WCUs MM-810:1 – MM-823:1, you can enter the query 81[0-9]|82[0-3]. This is a regular expression where the first expression, 81[0-9], means that we want our search to start with an '8' followed by a '1' and then any digit in range 0-9. The second part, 82[0-3], means an '8' followed by a '2' and then any digit in range 0-3. The two expressions are combined with a pipe characater ("|") which means logical OR. In other words we are looking for range 810-819 OR 820-823.

'''Note!''' If your WCU/resource group you are searching for has special characters (like '(' or '/') in its name you may need to escape these characters in order to get the desired result. Escape means putting a '\' before the special character. For example if you want to enter (and search for) the resource group name 'ABC(Alpha_Bravo_Charlie)' you need to write 'ABC$Alpha\_Bravo\_Charlie$'. Another example is when you want to list a WCU that contains "07-51" in its name. In this case you need to type "07\-51", otherwise the "-" character will make the searcher to search for a range of numbers.

For more info how to use regular expressions, see [https://en.wikipedia.org/wiki/Regular_expression#Standards Regular Expressions]

When you are filling in search criteria you can see in the top right corner how WICE says "Rows found:". That tell you how many assignments your search will find so you know if you need to narrow or broaden your search.

In the bottom right corner you have two binoculars. With these you can save and load your search criterias and shown columns for future uses. You can also set a view of criteria and columns as your default by hovering over the view you want and then pressing the pin button. There is also two magnifying glasses that can save and load your search results so even if their information change and can not be found with the same search criteria you can still find them. You can also pair a search with a view by going to your searches and then on the search click the binocular button and select which view you want to pair it with. You can also pair them going to your searches and press "Select search views" where you get a window with the option to pair your searches with views.

If you are using an older version than 2.45.0 you have 4 bars with calanders to the right of them. This is a function to search assignments by date of creation and last update. This function has been removed in 2.45.0 and does not work like intended in 2.44.8.

In 2.45.0 and forward there will at the top be a option to search assignments after their label. By selecting multiple labels you can search for more than one at the same time.

== The Result Section ==
The assignments are fetched when you press the "Search" button in the Tasks tab. Here we will go through the bottom part of the Tasks tab and the options for your previous search.
===Assignment Options===
You can right-click one or many assignments to get a menu with a range of options described below:
* "Show task description" will show you the description of the task that the assignment you right-clicked on belongs to.
* "Go to Vehicles Panel" will take you to the vehicles tab. When you are in the vehicles tab the car(s) you selected will be shown in the vehicles tab.
* "Go to Search Panel" will take you to the search tab. When you are in the search tab the WCU(s) you selected will be selected in the search tab.
* "Get/Show assignment" will give you a small pop-up dialog with some assignment information and a "Download assignment" button if a download is possible. If you choose to press "Download assignment" the assignment file will be downloaded to your computer in its original format.
* "Edit task" will give you the option to edit ownership and expiration date of the task. It will also show you the WCU(s) the task is running on.
* "Show car info" and "Show WCU info" will give you a pop-up showing you available info of the assignment car and WCU. Depending on which car/WCU you choose there will be different information available since cars/WCUs can lack information.
* "Show message" will show you the assignment's status message.
* "Plot route" will open a map in your current window. In that map you can see up to 100 of the cars registered positions during the last 24 hours or the last 100 registered positions. For more information about this read [[Plot Route Dialog]].

* "Event subscription" is an option where you choose to subscibe to a car, a WCU or an assignment. When hovering above "Event subscription" you will see three options, "Connect", "Assignment status" and "Result upload". With the option "Connect " you can subscribe to the selected car(s) or WCU(s) and get notified when their connection status changes. "Assignment status" and "Result upload" subscribes you to selected assignment(s) and gets you notified about status changes and when results are uploaded. You will se events when clicking on the bell symbol at the top which gets a red dot when theres new events from your subscriptions.

===Column Options===
The result section has many ways to sort, view and handle the result with the columns. When right-clicking a column you will get a window with different options for the column.
* "Sort Ascending" and "Sort Descending" will sort the assignments in ascending or descending order after the column's attribute.
* "Configure Sort" where you can add more levels of sorting so that it sorts for more than one thing in different priority. For example can you sort after task ID ascending and then sort after WCU ID descending. When a column has a sorting prefrens the option "Clear Sort" will appear which clears your sorting preferences for that column.
* "Columns" opens a window where you can select which columns you want shown and which you want hidden by checking or unchecking their corresponding checkboxes. If you remove a column with a filled search criteria that criteria will still matter when you make a new search. Also when you make the new search the column will reappear.
* "Group by" groups together the assignments that share the column's attribute value. When they are grouped there will be the option "Ungroup" that ungroups them.
* "Freeze" moves the column to the left corner and freezes it in position so it can be rearranged. If there is alraedy a frozen column till will move next to it as they go from left to right in chronological order. The "freeze" then becomes "Unfreeze" which revertes the freeze.
* "Export to excel" will export the columns and results into an excel file that will get downloaded.
* "Clear all fields" will clear all columns of their criteria.
* "Get help for this column" should take you here.

===Get result files===
When selecting a file you can view the result files by pressing "Get Result Files" if there are available result files. That will create a window where you can search, view and download result files. It is also possible to view result files from multiple assignments at the same time by selecting many assignments of the same type (Only possible for Signal Reader and MCD-Hub tasks).
====Searching result files====
The window will look different depending on what kind of assignment you selected watching. The different windows all share a lot of tools and have the same concept: to search and filter files. In illustration 6 you can see how a MCD-Hub result window looks. This is a great example as this window contains all different tools while all the others can be seen as an MCD-Hub window that does not need and therefore lacks some of the tools. There are some tools that all have and just like when creating a task the common ones are at the top. Below is a description of all tools followed by which assignment window that has them:

===== General search functions =====
[[File:Get Result files.png|thumb|400x400px|Illustration 6: The-MCD-Hub result file window.]]
At the top there are two boxes, labeled "Description" and "Filename", whereby you can search for files based on their description and filename. The "Description" box is disabled so that you can not type in it. When searching by filename it will search for actual result files, the not compiled (i.e. zip) files. Below there are two other sections with two checkboxes. The sections are labeled "From" and "To" and contain dates that can be changed by using the calendar next to the box. The files are filtered so only files between those two dates are shown. The checkboxes are labeled "Measurement Date" and "Upload to Portal" and only one of them can be checked. The checkboxes tell if the files will be filtered by measurement or upload date. There is also a checkbox labeled "Hide downloaded files" which will filter out already downloaded files but this button is disabled if the checkbox "Compline by portal update date" is checked. These tools are the same for all type of assignments and can be seen as marked green in illustration 6.

===== GPX inclusion =====
The checkbox "Include GPX" enables GPX files containing positioning data to be included when downloading result files. That means each downloaded result file will have a corresponding gpx file containing the route of the car when the assignment was executed. Note that the en date for the route is 24 hours after the start since assignments does not always have end dates. ETAS, Softhub, SignalReader and MCD-Hub assignments has this tool and its marked pink in illustration 6.

===== File type filters =====
There are three sections of checkboxes that are framed by a blue line and an outline checkbox labeled "Raw". These sections and the checkbox filter what type of files are shown. The framed sections represent one file type with their own sub-groups. The sections are labeled with what file type they filter. When the outline checkbox in the framed section is checked, it will show you that section's file type. When the respective outline checkbox is not checked, the other checkboxes are disabled as they represent the sub-groups for that file type. The "Raw" checkbox is simpler since it only indicates whether you want to show raw files and lacks sub-groups. As with the other search functions in the WICE portal, leaving all filters empty will result in everything being shown. The section labeled "Text" has three other checkboxes which will show you "Common", "Separate" and "All" text files. Note that not all text files have the subtype "Common" or "Seprate" and can only be shown in "All". The section labeled "MDF" has two other checkboxes which will show you MDF files "With module names" or "Without module names" (i.e. either with or without prefixes in the signal names). The section labeled "Vector" has two other checkboxes which will show you files referring to frames by "Frame ID" or "Frame name". Typically, the MCD-Hub, Softhub and Signal Reader measurement tools generate these file types (but note that Signal Reader does not have the "Raw" option). These tools are marked blue in illustration 6.

===== Compile by upload date =====
The checkbox "Compile by portal upload date" will compile result files into a zip file if they were uploaded at the same time. When the files are compiled some functions that usually work on result files work differently, or do not work at all. As mentioned before, you cannot search for the compiled file since it does not really exist, but is rather created on demand. But when searching with this option turned on, the compiled file will show up if one or more of the files it contains match the search criteria. This search feature is automatically turned on since you are often looking for a specific uploaded file. MCD-Hub, Softhub and Signal Reader has this option and it is marked yellow in illustration 6.

====Handling result files====
When you have selected the result file(s) you want different buttons will be active depending on the file. The buttons are above the column bar and it is where you download, view and convert result files.

"Get file(s)", "Get all files" and "Get log files" will open a dialog to [[Downloading Files|download]] selected files, all files or that dates log files. In the dialog you will get the option to add a description, when downloading result files you can also add plate number and/or VIN to the file name. Note that downloading log files from multiple result files will download only log files 24 after the oldest result files so download log files from result files one result file at a time.

"Save Headers" saves your current view of columns and files and saves it as default. This button has since been replaced by the two binoculars that are described in The Portal User View#The Search Fields Section. We therefore advice you to use the new and improved binoculars as save headers will be removed.

"Plot route" will open a map in your current window. In that map you can see up to 100 cars' registered positions during the last 24 hours or the last 100 registered positions. For more information about this read [[Plot Route Dialog]].

"View log files" will view log files from the selected file´s date. When viewing log files from multiple result files at the same time it will show you log files 24 hours after the oldest result file and not from both dates. you can always change the dates when viewing log files to narrow or widen the amount of files. When viewing log files you can read them by selecting a file and pressing "View file". There is also the option to "Get file(s)", "Save Headers", "Plot route" and "View file" who are all except "View file" described above. "View file" will open the log file in readable format in your current window. You can also filter log files like you filter result files by date, name and if they are downloaded or not. Note that when selecting to view log files from many files it will show log files from the oldest file's date and 24 hours forward.

"View file" will open the file in a readable format in you current window. If the file is compiled by upload date or not readable this button will not be enabled.

"Convert to text" will convert and download selected MDF file(s) to your computer. When doing this you will get a pop-up with the ability to add a description to your download. This is only availible for MDF files and this button can therefore only be found on assignments with MDF files.

"Preview data" will give you a data preview window where you can preview the selected file(s) data. To read more about how to use this window and all its functions read [[Preview data]].

New in v2.48

2018-06-26T14:54:53Z

Richard.wecke: /* Resources can now be moved directly between resource groups */

This page lists new and changed features in version 2.48 of the WICE Portal.

== Strict resource groups ==
Strict resource groups have been added to help manage measurement on large fleets of vehicles with minimum micromanagement.

== WCU as Wi-fi Access Point ==
A WCU can now be configured to act as a Wi-fi Access Point

== Stopping assignments ==
Stopping of assignments in the Tasks tab have been reworked to be more intuitive and work with strict resource groups.

== Canrecorder ==
Canrecorder now supports up to 6 CAN buses with CAN frame filters per CAN bus. For a closer look at how to set up a Canrecorder task, see [[The Portal User View#CAN-recorder|The Portal User View]]

== Default CAN channel should now be visible in the interface for IDC, SoH,SWDL and VinReader. ==
Users can now set a default CAN bus (Default CAN channel), on which request from the assignments are sent to. The actual CAN buses are selected from the Configuration. The settings can be found in each respective tool (found in the Modules panel).

== Support for WCU reporting back the status for its configurations ==
The WCU can now report the result of updating both the tool-configuration as well as the WCU-configuration, back to the user. The different statuses for updating are: Ok, Warning or Error. Additional text can be added, shown when hovering the mouse pointer over the status indicator.

== Added functionality to MDF preview/monitor ==
User can now :
* Double-click a preview plot to add it the master plot.
* No module names in the preview plot, but still kept in the master plot.
* Monitoring is limited to 20 points of data per series in the map.

== Possible to search for empty fields in the Vehicles panel ==
It is now possible to search for empty fields in the Vehicles panel by entering the regular expression "^$". Any field that is a string can be searched this way except for VIN and VCU ID.

== Improved IDC-assignment CAN mapping ==
It is now possible to:
* Map all rows to one CAN bus.
* Select a partial amount of all rows and map them to one CAN bus.

== Resources can now be moved directly between resource groups ==
It is now possible to move resources between resource groups without having to first remove them from the resource group they currently belong to. Users can simply mark the resources they wish to move and press the "Add resource to resource group" button. A dialog will appear informing that resources will be removed from the group they currently belong to. By pressing "OK", the transaction will complete and the resources will be moved to the desired resource group. See [[The Portal Administrator View#Resource Groups|The Administrator Portal View]] for more.

== Support for Video preview ==
To learn more about configuring the Video module and creating Video assignments, see the [[WICE video|page about WICE Video]].

== Support for searching with the AND operator between labels ==
Users can use search expressions containing the operator AND when searching via labels.

== Get the resource group from contained member ==
Users can search out the resource group that a resource belongs to, in the Vehicles panel.

The Portal Administrator View

2018-06-26T14:47:02Z

Richard.wecke: /* Requirements for moving or adding a resource to a strict resource group */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T14:45:11Z

Richard.wecke: /* Resource Groups */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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 groups|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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T14:44:38Z

Richard.wecke: /* Resource Groups */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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 groups|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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T14:44:19Z

Richard.wecke: /* Resource Groups */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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 groups|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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T14:43:39Z

Richard.wecke: /* Resource Groups */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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 groups|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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T14:42:10Z

Richard.wecke: /* Resource Groups */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a 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|Illustration 39.2: Dialog informing that a WCU will be 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|Illustration 39.3: Adding or moving a WCU to a 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 groups|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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T14:41:02Z

Richard.wecke: /* Resource Groups */

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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:AddWCUtoResourceGroup.png|thumb|Illustration 39.1: Adding resources to a group.|left]]
==== 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|Illustration 39.2: Dialog informing that a WCU will be moved to another resource group.|left]]
==== 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|Illustration 39.3: Adding or moving a WCU to a strict resource group.|left]]
==== 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 groups|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==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

The Portal Administrator View

2018-06-26T12:45:16Z

Richard.wecke: /* The Resource Groups 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 Search Tab==
[[File:Admin stop assigment.png|thumb|200x200px|Illustration 32a: Stop running assignment]]
[[File:Admin force stop assignment.png|thumb|200x200px|Illustration 32b: 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.

Illustration 32a 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 illustration 32b, 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. Illustration 33 shows an example of this view. The table header along with the buttons “Edit Description” and “Get Log Files” are explained in the page for '''[[Vehicles]]'''.

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

[[File:42vehiclestab.png|none|left|frame|Illustration 33: The administrator's view in the WCUs tab.]]

===The New WCU Dialog===
[[File:Illustration34.png|frame|Illustration 34: The Add New WCU Dialog.]]
There are two ways that a WCU can enter the portal. The first is if you click the “New WCU” button and the second is the first time a WCU connects to the portal it registers itself. Ideally you will never have to add a WCU to the portal but just as a safety step you have the opportunity to add it yourself. When clicking the “New WCU” button the dialog in Illustration 34 opens up. You must enter the ID of the WCU as this is a unique identifier and you will be notified if the ID is already present on the portal. The description is optional but may be handy to remember which WCU it is.

===Edit the WCU Configuration===
[[File:Wcu config1.png|150px|thumb|frame|Illustration: Modules.]]
[[File:Wcu config2.png|150px|thumb|frame|Illustration: Connection.]]
[[File:Wcu config3.png|150px|thumb|frame|Illustration: WCU.]]
[[File:Wcu config4.png|150px|thumb|frame|Illustration: Power management.]]
[[File:Wcu_config_wake_on_can.png|150px|thumb|frame|Illustration: Wake On CAN]]
[[File:Wcu config5.png|150px|thumb|frame|Illustration: Upload.]]
You can edit the configuration of the WCU from the portal. Simply click on '''Edit Configuration''' to open up the window in "Illustration: WCU Configuration: Modules". The WCU configuration window is divided into five tabs where each tab is described below.

====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 "Illustration: Connection" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Internet Service Provider (ISP)
| Which ISP to use when multiple SIM cards are installed
|-
| style="font-weight: bold;" | WICE portal address
| The server that the WCU should use for fetching new assignments etc.
|-
| style="font-weight: bold;" | DRO Server
| The server to connect to when doing a Diagnostic Read-Out.
|}

====WCU====
This tab can be seen in "Illustration: 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.

====Power Management====
[[File:Periodic wake up time.png|thumb|frame|Illustration: Perodic wake-up]]
This tab can be seen in "Illustration: 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 as shown in "Illustration: Wake On Can".
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 illustration "Perodic wake-up".



====Upload====
This tab can be seen in "Illustration: Upload" and the tab content is described in the table below.
{| class="wikitable"
| style="font-weight: bold;" | Mobile upload limit
| Defines the maximum data size that should be transferred via the mobile network. If the data size is larger than that the WCU will wait until a connection to a local network can be established. The size is in Mbytes.
|-
| style="font-weight: bold;" | Post run grace timeout
| The number of seconds to wait before communicating with the MCD-Hub and portal, if the ignition is turned off.
|-
| style="font-weight: bold;" | Upload timeout
| The maximum number of seconds the WCU should upload data before stopping.
|-
| style="font-weight: bold;" | Erase error code
| If turned on the error codes in the car will be reset.
|-
| style="font-weight: bold;" | Upload data at boot
| Uploads data when the WCU boots up
|-
| style="font-weight: bold;" | Upload data at ignition off
| Uploads data when the car is turned off
|}
<gallery widths="150px" mode="nolines">
File:Wcu config1.png|Illustration: Modules.
File:Wcu config2.png|Illustration: Connection.
File:Wcu config3.png|Illustration: WCU.
File:Wcu config4.png|Illustration: Power Management.
File:Wcu_config_wake_on_can.png|Illustration: Wake On CAN
File:Wcu config5.png|Illustration: Upload.
</gallery>
Version >= 2.41 of the portal has a new tab named I/O. You can read more about in [[I/O_configurations]].

===The Edit Car Dialog===
[[File:Illustration37.png|frame|Illustration 37: Edit Car]]

To edit the information about a car, press the “Edit Car” button. The dialog in Illustration 37 opens up.
The one entry you can not edit is the VIN entry. If you need to edit that you must instead create a new car.
In order for the portal to be able to translate Diagnostic Trouble Codes into a human readable format, you must choose a diagnostic DB file to be used. It is important to select the correct one as the diagnostic trouble codes read out might be translated incorrectly or (more probable), not at all. It is also important to select the right type of car using “Car type”. This controls the number of CAN buses and the number of Ethernet networks, if any, in the car. The “Active” check box controls whether the car should show up in tables and searches in general concerning cars. A car can never be removed as it has probably been involved in measurements but to recall an inactivated car you must actively select to view inactivated cars.

It is possible to update several cars at once by selecting multiple cars and then press the “Edit Car” button. By doing this you can selectively make changes to attributes of all the selected cars at once. To do this, the dialog is extended as can be seen in Illustration 38 below.

[[File:Illustration38.png|frame|Illustration 38: Edit Car|center]]

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

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

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

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

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

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

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

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

[[File:Illustration39.png|frame|Illustration 39: Adding resources to a group.|left]]
To add resources to a resource group you start by selecting the resources you are interested in adding to a resource group. Resources already added to a resource group will render the corresponding add button disabled.

When you are satisfied with your selection you press either the button “Add WCU(s) to resource group” or “Add car(s) to resource group”. Pressing any of those buttons 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 three 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 but in case you wish not to, simply uncheck that checkbox. There are also situations when there are no module configurations for some modules and if you press “Add” you will be prompted about that. If you for some reason do care about that you can check the “Ignore non existent tools and configurations” checkbox.

==Modules for the WCU==
Each WCU supports a number of modules. The modules are software components realizing specific functions, such as a measurement tool, a data source or software component. Some modules correspond to external measurement devices connected to the WCU, whereas other are built-in. This makes it possible to add new peripherals to the WCU for handling various tasks in acquiring measured data from a car. The set of currently available modules are:
# Blue piraT
# Canrecorder
# DoIP
# ETAS
# GPS
# IDC
# MCD-Hub
# Rapid Prototyping (RP)
# Signal Reader
# SoftHub
# Software Download (SWDL)
# State of Health (SoH)
# Uptime
# Vinreader

To deal with each module's configuration a new view is presented below. To open this view, press the button “Modules” as shown in Illustration 33 on [[#The Vehicles Tab]].
In the illustration above there are a set of tools present. Each type is grouped on the left side using a stack panel. Select the connected MCD-Hubs by selecting the MCD-Hub stack and select (click) the Canrecorder stack to see the canrecorders connected a so fourth.

[[File:Illustration40.png|frame|Illustration 40: View for handling tool configurations.|center]]
Each tool has its own entry in each of the stacks. In Illustration 40 above 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 tool description”. To reload the set of available tools for both MCD-Hub and Canrecorder, press the “Reload tools” button.

===Configure the Canrecorder Module===
The configuration for the Canrecorder module is shown in Illustration 41 below. There are four fields of which two are editable. In order for the canrecorder to work you need to set the high- and low speed CAN bus. The update date says when the last configuration was enabled and the canrecorder version says which version of the canrecorder software is used.
[[File:Illustration41.png|frame|Illustration 41: Configuration options for Canrecorder.|center]]

===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===
[[File:Illustration42.png|frame|Illustration 42: Settings for the Internal Diagnostic Client (IDC).|center]]
The IDC module can be configured with which CAN bus to communicate with the vehicle. You can actually even choose both where it will first try the Ethernet network (ETH), if it exists, and the CAN bus. If the car type in question does not have an Ethernet network, only the CAN option will appear.

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

===Configure the Uptime Module===
[[File:Illustration43.png|frame|Illustration 43: Settings for the Up-time module.|right]]
The module is used to report how much and how long the WCU is running. First of all you can enable/disable the functionality all together with the “Enabled” check box. Next is how often the up-time should be logged in seconds. The second check box, “Monitor enabled” is used when you would like the module to report its up-time in real-time and the interval for that, also in seconds.

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

===Configure 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”. It is currently set at an update rate of once every second.

===Configure the RP Module===
From version 2.35 of the portal there is a possibility to upload up to three files to configure the RP module. The three files are:
# Configuration file
# Certificate file
# Binary file

[[File:Illustration44.png|frame|Illustration 44: Settings for the RP module.|center]]

For information on how to use the RP module, see the [[WICE RP Manual]] and the [[WICE RP How-To]].

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

==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” and “Users”.

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

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

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

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

To disconnect a WCU and car you simply press the icon for wither of the WCU or car.
See Illustration 45 below for an example.

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.

[[File:Illustration45.png|frame|Illustration 45: The connect Car to WCU tab.|center]]

===The User Administration 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 Illustration 46 below.
The eight columns are:
[[File:Illustration46.png|frame|none|left|Illustration 46: The 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====
[[File:Illustration47.png|frame|Illustration 47: The New User Dialog]]
By pressing the “New User” button the dialog in Illustration 47 below appears. 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. Click the “Add” button to add the user or change you mind by clicking “Cancel”.

====The Edit User Dialog====
You can at any time modify a user by pressing the “Modify” button to bring up the dialog in Illustration 48 below. 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.

[[File:Illustration48.png|thumb|frame|Illustration 48: The modify user dialog.]]

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

====The Change Password Dialog====
[[File:Illustration49.png|thumb|frame|Illustration 49: The change password dialog.]]
To change a user's password, press the “Change Password” button and the dialog in X Y will appear. It is pretty straight forward as you type in the new password in the “New password” entry and you need to confirm it by typing it again in the entry below it. If you are satisfied, click the “Change” button or the “Cancel” button if you decide not to change the password.

====The Show Secret Window====
[[File:Illustration50.png|thumb|frame|Illustration 50: The 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 Illustration 50. 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.

{{: Roles and permissions}}
===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 Illustration 56 below.
[[File:Illustration53.png|left|frame|Illustration 56: The 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 Illustration 57, below.
[[File:ResourceGroupsPanel.png|left|frame|Illustration 57: The resource groups panel.]]
 
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|Illustration 58: 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 Illustration 59 below, you see a set of resources for a resource group.
[[File:ManipulatingResourcesInResourceGroup.png|left|frame|Illustration 59: Manipulating resources in a 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 Illustration 39 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 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 Illustration 60 below.
[[File:Illustration57.png|left|frame|Illustration 60: The WCU Status tab.]]

File:ManipulatingResourcesInResourceGroup.png

2018-06-26T12:43:25Z

Richard.wecke: Richard.wecke uploaded a new version of File:ManipulatingResourcesInResourceGroup.png

Manipulating resources in a resource group

File:ResourceGroupsPanel.png

2018-06-26T12:37:20Z

Richard.wecke: Richard.wecke uploaded a new version of File:ResourceGroupsPanel.png

The Resource Groups panel

File:CreateNewResourceGroup.png

2018-06-26T11:57:21Z

Richard.wecke: Create a new resource group

Create a new resource group

File:ManipulatingResourcesInResourceGroup.png

2018-06-26T11:56:44Z

Richard.wecke: Manipulating resources in a resource group

Manipulating resources in a resource group

File:ResourceGroupsPanel.png

2018-06-26T11:56:04Z

Richard.wecke: The Resource Groups panel

The Resource Groups panel

File:ConfirmMovingResourceToResourceGroup.png

2018-06-26T11:46:42Z

Richard.wecke: Confirmation dialog of moving a resource between resource groups

Confirmation dialog of moving a resource between resource groups

File:AddWCUToStrictResourceGroup.png

2018-06-26T11:46:11Z

Richard.wecke: Add a WCU to a strict resource group

Add a WCU to a strict resource group