The Portal User View
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
To access the WICE portal you need to log in with your WICE username and password. If you have not yet received a username and password, contact your local WICE portal administrator.
If enabled, you may have to enter a one-time password when logging in. This enhances the security by providing something called two-factor authentication. The one time password is typically generated from an app in your smart phone. There is also a program for a desktop computer to generate the one time password. For Android, iPhone and Blackberry you can download an app called “Google Authenticator” to generate these one time passwords for you. An internet connection is not needed in order to generate the passwords. To log in to an account you need to enter your login, ordinary password and the current 6 digits generated by the app. A new 6 digit number is generated each 30 seconds.
To simplify logins from the same computer, typically the one at work, you can tick the check box “Remember me”. If you tick this before you hit the login button when using the one time password, you will be remembered by the portal for the next 30 days. The next time you login from the computer you only have to enter your password. When the 30 days have passed you will once again have to enter a one time password to 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 de-assign 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.
Tasks Tab
In the Tasks tab you can search for tasks, view and manage the tasks, 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.
Columns
| Task ID* | The nummeric Task ID. |
|---|---|
| Assignment name* | The assignment name. |
| Type* | Different options for task 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 task's uploads given in Kbytes. |
| Plate number* | The vehicle's plate number. |
| Status* | Different options for task 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 task's last upload. |
| VIN* | The vehicle's Vehicle Identification Number. |
| Proto number* | The proto number. |
| Project* | The project ID. |
| TSU* | The TSU ID. |
| Car comment* | The vehicle's comment/description. |
| Series* | The series attribute. |
| Message* | The task's status message. |
| WCU name* | The name of the WCU. |
| Task creator* | The original creator of the task. |
| Task owner* | The current owner of the task. |
| Expire Search date | The date the task will expire. |
| Creation date | The creation date of the task. |
| Resource group* | The resource group the WCU was part of when the task was created. |
| *Searchable column. | |
Search columns with regular expressions
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 Regular Expressions
In the "Type" column a search is performed based on a checklist drop down menu with the default choice of all types being selected. If there is a need to solely select one type, it is possible to simply double-click on its corresponding field, given that it is already checked, and all other types will be deselected.
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 tasks 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. To read more about this, click here.
At the top is a field for 'Search by labels'. Any labels selected here will be appended to the search criteria assembled from the columns. It is also possible to search only by labels.
It is important to know that labels on resources in the Tasks tab are the labels associated with the WCUs and vehicles when the tasks was submitted. Labels added after the task was submitted will not be visible here or yield any search results.
The Button Section
At the bottom of the table is an assortment of buttons available for you. From left to right are:
- Get Result Files, handles result files generated by the various tasks, is described below
- View Task, some aspects of a task can be changed while the task is running, see .. for a description per task type
- Get Log Files, shows a panel where the internal log files generated by the WCU can be viewed.
- Plot Route, a set a routes defined by the drive cycles can be viewed on a map. See plot route for further information.
- New Task, creates a new task for the selected WCUs. See creating tasks for further explanation.
- Refresh, updates the table with information regarding uptime, status and more.
- View Vehicle, opens a dialog showing the vehicle as it looked like when the task was created.
- Monitor signals, if for the selected task a set of signals are monitored, these can be viewed in real time by pressing the button.
The Result Section
Tasks are continuously fetched are you type the search criteria into the fields. Here we will go through the bottom part of the Tasks tab and the options for your previous search.
Task Options
You can right-click one or many tasks to get a menu with a range of options described below:
- "Show task description" will show you the description of the task that you right-clicked.
- "Go to Vehicles Panel" will take you to the Vehicles tab. When you are in the Vehicles tab the vehicles 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.
- "View task" will give you a small pop-up dialog with some task information and a "Download assignment" button if the task has an assignment that can be downloaded. 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. Additionally,from version 2.87.0 it is possible to modify the values of the labels. However, it's important to note that system labels cannot be edited.
- "Show car info" and "Show WCU info" will give you a pop-up showing you available info of the task vehicle and WCU. Depending on which vehicle/WCU you choose there will be different information available since vehicles/WCUs can lack information.
- "Show message" will show you the task's status message.
- "Plot route" will open a map in your current window. In that map you can see up to 100 of the vehicles 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 subscribe to a vehicle, a WCU or a task. When hovering above "Event subscription" you will see three options, "Connect", "Task 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. "Task status" and "Result upload" subscribes you to selected task(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 tasks 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. You can for example sort on task ID ascending and then sort on WCU ID descending. When a column has a sorting priority 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 tasks 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 already 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 reverts 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 show a panel where you can search, view and download result files, see Figure "Get Result File Window". It is also possible to view result files from multiple tasks at the same time by selecting many tasks of the same type (Only possible for Signal Reader tasks). To remove one or several files, simply select them in the grid, right click and then select the corresponding option.
Searching result files
The window will look differently depending on what kind of task you selected to view. The different panels all share a lot of tools and have the same concept: to search and filter files. In Figure "Get Result File Window" you can see how a Signal Reader results window looks. Below is a description of all tools followed by which task window that has them:
General search functions
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 "Compile by portal update date" is checked. These tools are the same for all type of tasks and can be seen as marked green in Figure "Get Result File Window".
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 vehicle when the task was executed. Signal Reader, ETAN and SoftHub tasks have this tool and its marked magenta in Figure "Get Result File Window".
File type filters
There are three sections of checkboxes that are framed by a blue line which filter the shown file types. The framed sections represent one file type with their own sub-groups and they are labeled according to 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. 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 Signal Reader measurement tool generates these file types. These tools are marked blue in Figure "Get Result File Window".
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. Signal Reader and SoftHub have this option and it is marked yellow in Figure "Get Result File Window".
Label Search
It is also possible search by result file labels using the section marked in red in Figure "Get Result File Window". It is, however, only possible to add labels by the use of server triggers on Signal Reader and Softhub tasks. If there are no tasks of either of these type for the selected WCUs this search option is hidden.
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 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 further described here. 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 vehicles' 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 tasks 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.
Removing result files
To remove one or several files, simply select them in the grid, right click and then select the corresponding option.
Creating a Task
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of task you want to create. Note that it is not possible to create a new task for a WCU which has the system labels ''shelving_in_progress'' or ''shelving_done''. However, if the WCU has the latter label, it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of tasks available. Remember that not all of the task types will be available as this depends on customer configuration and some types might not be enabled in the portal.
To learn about how to add resources to the task, check here.
Arcos
The WICE system can interact with external loggers as well. From version 2.71 the portal can interact with the Arcos-logger from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension ".ccmc". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the Arcos - no upload will be required.
Since version 2.79.0 Arcos tasks can now have software version validation in the same manner as described for the M-Log task (see Software version validation).
Area5
Area5 tasks are used to read out data from the memory of ECUs.
Assignment: To create a new Area5 task you first have to create an Area5 assignment in the Area5 Assignment Editor.
Validate ECU SW version on WCU: By checking this box, the WCU will validate that the ECU SW version of the task and the actual ECU are the same before starting the task. If they are different, it will not start the task.
Trigger Expression: The task can be started by an expression. This option lets the user specify start trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). For an explanation of trigger conditions look here.
Sync Signal: It is possible to specify a signal with given values that will be sent when the Area5 task starts and stops. This can be used to synchronize the Area5 read-out with external measurements systems like the M-Log.
Audio
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:
- Trigger button: to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.
- Signal reader: initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader recorder is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the audio recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected.
- Expression: Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of triggers look here.
- Audio level: Start the trigger once the microphone registers volume above a certain threshold.
- None: start the recording as soon as possible.
In addition to this, you can set the pre-trig time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.
A maximum duration of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as Alkit Confero.
There is more information about audio in WICE here.
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.
Blue piraT
The blue PiraT is a measurement system from Telemotive AG that can be configured with measurement set-ups, and data accessed through the WICE Portal. Note that to use the blue PiraT module, the WCUs to be used need to be preconfigured with a special software package (i.e. an "extra bundle"). Contact Alkit Communications in order to set this up.
CAN-recorder
Canrecorder is a measurement module that allows CAN frames to be captured and logged.
1. In the grid, select which bus (or buses) to record from. By clicking below active column or select a row and click on “Toggle” button.
2. To apply filters on specific CAN buses, select a row and click on “Edit filter”. There it is possible to select one specific frame or several by separating them by “,”. It is also possible to select a range between frames by using “-”. The value can either be decimal or hexadecimal. A example of a filter: “1, 0x12-0xFF”
3. Below the grid settings for how long the recording should be and how many shots. If not using shot count, infinite result files will be created as long as the units are on.
Scheduling
For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached. By selecting the "On ignition" checkbox, the task will be performed once on ignition. If delay is above 0 then the task will be performed once the configured amount of seconds have passed after ignition.
To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the Vehicles panel. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.
Diagnostic Log and Trace (DLT)
DLT itself provides a log and trace interface, based on the standardised protocol specified in the AUTOSAR standard 4.0 DLT. A DLT task in the WICE Portal makes it possible to collect such logs in a vehicle where this functionality is available and transfer the data to the WICE portal where logs can be downloaded for further analysis. For a more in-depth description, you can go here.
Basically the WCU is connecting to one or more DLT Daemons and unique filters can be applied to each daemon, filtering out specific log messages.
So when creating a DLT task on WCUs with software version 2.72.0 or later the number of daemons can be specified and for each daemon the following needs to be specified:
- Daemon address - the IP-address in order for the WCUs DLT client to find the daemon.
- Daemon port - which port on the address the daemon is at.
- Filter configurations - filter expressions to be applied on the log messages. If left empty no filter is applied. For an explanation on how to write filter expressions, see here.
Older WCUs
For WCUs with software version earlier than 2.72.0 only one daemon is supported and only filters can be configured when creating a DLT task. To specify the daemon address and port go to the DLT Module instead.
ETAS
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.
When creating an ETAS task, the task description file you select must be a .exp file.
Ethernet capture
This kind of task is used to capture packet data from one of the ethernet interfaces on the WCU. The basics for this kind of task is that you choose the interface you would like to capture from and a capture expression to filter which packets you are interested in. The results from this task type is pcap files. To read more about this task type, go here.
File fetcher
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.
The following needs to be specified when creating such a task:
- File path - One or several paths to a files or file-containing directories on the unit's file system. This specifies which files that will be fetched.
- Username - To log in to the unit.
- Password - To log in to the unit.
- IP address - To find the unit.
- Port - To find the unit. Default is 22, but can be changed.
Furthermore, the task also allows the use of a proxy.
To use a proxy, the Use Proxy checkbox has to be checked, and the following must be specified:
- Proxy Username - To log in to the proxy unit.
- Proxy Password - To log in to the proxy unit.
- Proxy IP Address - To find the proxy unit.
- Proxy Port - To find the proxy unit. Default is 22, but can be changed.
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 can be created as an assignment in the Assignment tab, alternatively can be uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.
IPEmotion RT
The WICE system can interact with external loggers as well. From version 2.72 the portal can interact with the logger IPEmotion RT from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension ".irf". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.
Since version 2.79.0 IPEmotion RT tasks can now have software version validation in the same manner as described for the M-Log task (see Software version validation).
LPD
This type of task is ultimately handled by a separate App in an iPhone or iPad. The WICE system simply makes this task available to the App through a REST interface running on the WCU. The task consists of a specially crafted excel file. When the file is uploaded to the WICE portal it is validated to make sure that it can be read by the App.
From version 2.83.0 of the WICE portal the task measurement file can be updated via the View Task function in the Tasks tab and a dialog as shown to the right will appear. By pressing the "Edit" button in the lower right corner, you will be presented with the possibility to upload a new measurement task file. This is shown with a red triangle in the illustration on the right.
M-Log
The WICE system can interact with external loggers as well. One such logger is called M-Log from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the MLOG - no upload will be required.
Software version validation (Available from version 2.74.0)
The measurement assignment for an MLOG is created using an external tool to WICE. An assignment is created with a certain version of the ECU software in mind for each ECU in the assignment. In order for the assignment to work it might be important that the ECU software version in the vehicle matches the software version of the ECU it was created for. In WICE, you can ask the system to read the current software version for each ECU which is stored and can be viewed, e.g. via the ECU list. As WICE cannot know which software versions the assignment was created for, the user can supply this to WICE. By doing that, WICE can validate the entered software versions against what has been read out for each vehicle and thus aid the user in making sure that an assignment will work once it will run.
To make the validation possible the user enters a ECU by its address, not the name. To help find out the address for an ECU you can go to the ECU list to find the address of a specific ECU. Have a look at the illustration, Entering ECU software version, to see where in the dialog this is entered. On the top you enter the ECU address on the left and what software version is expected on the right. When satisfied, press the "Add" button. The data you just entered will be added to the table and evaluated against what the WICE system has read out from the vehicle. In the example to the right something is incorrect which is indicated by the yellow color. To see the exact reason, simply use the cursor to see the specific message.
A negative validation in not enforced in the sense that you cannot run the assignment but rather an indication that it might not work as expected. You can always go ahead and press "Submit".
MQTT
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.
Rapid prototyping
A Rapid prototyping (RP) task makes it possible to download RP binaries to multiple WCUs and keep track of the result files the RP task might produce. For more information about RP, see WICE RP How-To and WICE RP Manual.
The rapid prototyping tab can be seen in Figure "Rapid prototyping task".
An RP task must consist of at least an 'RP binary' or a 'Web application zip file'.
SoftHub
The SoftHub is a measurement system that can be run either as a stand alone unit or as a software module on the WCU, with functionality similar to the Signal Reader module. A SoftHub task is created much in the same way as a Signal Reader task.
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task.
The SoftHub task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add server triggers to the task that will trigger and add a suitable label to the corresponding result file. Read more about this here.
Signal Reader
Signal Reader is a data capture module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data, and ECU-internal signals read by CCP or XCP. To create a Signal Reader task you proceed as follows:
1. You either select an assignment file of .haf format, or choose an assignment created in the assignment creator (see Signal Reader Assignment Wizard). Your current choice will be displayed in the "Chosen file" field.
2. When you have selected an assignment and one or more WCUs, the CAN buses defined in the assignment and on the WCU will be mapped. If they can be automatically mapped a green check symbol will be displayed, otherwise a red cross will be displayed. Clicking the mapping button will open the mapper. In the pop-up window you will have to map the different buses to each other manually and then save. Once this is done correctly, the red cross will become a green check mark, indicating that the mappings are ready to be automatically applied upon submit. Read more about this in I/O configurations and Mappings.
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting "Monitor signals". When selected, two boxes will appear under the task description. In the left one you search for signals and drag them over to the right one where the signals to be monitored are listed. You can later see the monitored signals by pressing the Monitor Signals button either in the Tasks tab or in the Vehicles tab. It is also possible to copy the signals text in the bottom right corner of the right box. Next to the copy text button you can also paste signals as text where the pasted signal names will be matched against the list of unselected signals
4. You can choose if you want the signals to have their data source names as a prefix (e.g. CAN1.EngineSpeed instead of EngineSpeed).
5. The Signal Reader task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add Server Triggers to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this here.
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.
The Signal Broker
Signal Reader can act as a Signal Broker for other software components. For instance, the audio and video modules relies on the Signal Broker API of Signal Reader for evaluating start and stop trigger expressions. Moreover, the Signal Broker gives programmatical access to signals for Rapid Prototyping tasks. Read more about this in WICE Signal Broker API.
Files containing references to sequence files
If the measurement file contains references to sequence files, you are also required to select these in order to run the task. The portal scans the .haf file for such entries and presents this to you, see illustration 4.2. Click the button for each sequence file reference to upload each sequence file needed. Some requests in the sequence file may be for reading DTCs, and in such cases you can select the option of also reading associated Snapshots or Extended data. An example of this can found in Figure "Sequence Files References in .haf File".
Here, the .haf file contained two references to sequence files. As no sequence files have yet been uploaded, the selection for reading snapshot or extended data is grayed out. In Figure "Sequence File with Functional Query" we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read Extended data. It is also possible to select both Snapshots and Extended data.
WICE internal signals
In addition to CAN and FlexRay signals, a number of internal signals (i.e. internal to the WCU) are also available. The following WICE-internal signals are supported: WICE Internal Signals
SoH
A State of Health (SoH) task collects specific status information from vehicles. You select which information you want the task to collect by filling in one or more of the checkboxes shown in Figure "SoH". The number of checkboxes shown can vary depending on the WICE installation. In order for SoH data to be correctly interpreted, relevant description files (e.g. SDDB) for the vehicles executing the SoH task may have to been available. To add such a description file for a vehicle, see The Edit Car Dialog.The six different options are:
- Mileage
- Voltage
- Read ECU software numbers
- Read ECU DTC:s (optionally including 'Snapshot' and 'Extended data')
- Read OBD-II PIDs
- App Diagnotstic Db Part Num
- DM1, Diagnostic Message using the j1939 protocol
- Odometer, reading the odometer using the j1939 protocol (available from WCU version 2.63)
- Clear DTCs.
- If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)
- If this option (Clear DTC) is chosen it is optionally possible to set a PIN code for unlocking a gateway module - e.g. Vehicle Gateway Module (VGM). (Available from WCU version 2.66)
- Engine hours, reading engine hours using the j1939 protocol (available from WCU version 2.64). The result for this can be read in the generated j1939-file from the task. It is a text type of file. In addition, a system value label called 'engine_hours' (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle.
This task can also be scheduled in the same manner as described for the Canrecoder task.
Some selections above might not be available to you as this is a configuration setting depending on customer.
SWDL
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. ff:00:1a:2c:77 (or alternatively, omitting the colon separator, ff001a2c77). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table.
SWDL tasks can optionally include a pre-update sequence file and/or a post-update sequence file. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.
SWDL tasks can optionally include one signature file (containing checksums). The file is assumed to be an xml file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)
SWDL tasks can optionally include a VGM unlock access control mechanism, with a PIN code for the VGM node. This is specifically for vehicles requiring this kind of access control for ECU re-programming.
By checking the box Run SoH after completion it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "Use Vehicle Pin mappings". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes here.
SWDL tasks can optionally contain a Trigger Expression which must be fulfilled within a specified time limit ("Wait time") for ECU re-programming to be allowed. The trigger expression follows the same syntax as Signal Reader trigger expressions (or Server Triggers, audio/video triggers), and should be built up from signals being measured in a Signal Reader assignment. The user must make sure that there is a Signal Reader assignment on the WCUs of the SWDL task, with the signals of the trigger expression being measured.
It is also possible to choose to ignore checksums and/or disable pre-programming using the corresponding checkboxes.
The SWDL module can be configured to perform SWDL either over CAN or over Ethernet (DoIP).
Video
A video task makes it possible to record and monitor live video from one or two cameras attached to a WCU. You can trigger recording of video in four ways:
- Trigger button: To initiate the recording you need to attach a button to the WCU in order to start in the video recording.
- Signal reader: Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader recorder is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the video recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected.
- Expression: Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of how to enter triggers, have a look here.
- None: start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)
In addition to this, you can set the pre-trig time (not valid in the cases of the 'None' trigger option above). As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the video has already been recorded for the number of seconds specified.
A maximum duration of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.
If monitoring of video from a WCU is enabled, a live video stream will be transmitted which can be viewed using a RTP-based video tool, for instance Alkit Confero. This task can also be scheduled in the same manner as described for the Canrecoder task.
Read more about the video support in WICE here.
Applicable for all types
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a JMS API. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in SoH.
Site specific features
Announce result file availability
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a JMS API. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in SoH. Starting from version 2.87.0, there's a new 'Announced On' column that keeps track of when the result file was announced.
Retention time
This function works by setting a retention time in days which simply says that data coming in from the task, i.e. result files and positions will be kept the set number of days from when the data was collected. If, e.g. setting the retention time for an task to 30 days, will keep data until it is 30 days old where it will be automatically removed. See image.
It is possible to set a default retention time for resource groups. To do this, add a global value label named RETENTION_TIME to the resource group and give it an appropriate value. This value will then be used as a template value when creating a new task for this resource group. If multiple resource groups have this label and they have different values, the one with the lowest/shortest retention time value will be chosen as the template value.
Stopping assignments
The tasks tab provides options to stop measure tasks in multiple ways. These are explained below.
Tasks can assume multiple states
| Pending | The task is waiting for the WCU to download it. |
|---|---|
| Running | The WCU has downloaded the task and it has started. |
| Warning | The task is running on the WCU, but has reported warnings. |
| Error | The WCU has attempted to start the task, but has reported back major problems (that may have prevented it to run). |
| Stop pending | The WCU still has the task applied, but will stop it next time it connects to the portal. |
| Stopped | The WCU has stopped running the task. |
Resume Task
Used to undo the stopping of an task. This is only usable on Stop Pending tasks, and reapplies the task so that the WCU will continue running it. If there is another task of the same type currently in Pending for that WCU, that task is changed to Stopped, and will never be downloaded by the WCU.
Cancel Task
Used to undo the application of a new task. Only useable on Pending tasks. The task is instantly Stopped and if there is a task of the same type currently Stop Pending it reapplies that task and changes the status back to Running.
Stop Task
Stops the task without replacing it, making the WCU not run anything of that task type. Useable on Pending, Running, Warning, and Error. Pending tasks instantly enter a Stopped state while giving the WCU a stop command. Running, Warning, and Error tasks enter a Stop Pending state, waiting for the WCU to report it has stopped before changing state to Stopped.
Force Stop Task
Force stopping a task is an Admin feature meant for WCUs which have been physically disconnected by an operator while having an active task. In this situation the WCU will not report to the portal that it has actually stopped the task (since it will not turn on). In this case, this feature can be used to place the task in Stopped for tracking purposes. This can only be used on Stop Pending task. If you wish to force stop a running/warning/error task, you need to stop it first (using Stop Task).
Note that this will not affect the actual WCU in any way.
Stopping tasks and strict resource groups
You can use these features on strict resource groups to stop all tasks of that type running on the WCUs in that group.
Stop Task will place all the tasks of that type in either Stop Pending or Stopped based on their status (see Stop Task).
Force Stop Task 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 Task).
Note that Resume Task and Cancel Task can not be used on strict resource groups.
Search Tab
The 'Search' tab makes it possible to search for and download result files and log files without first searching for a specific task. The tab is split into three portlets where each portlet can be expanded or minimized to make more space for the other windows.
The portlets are Search, Results and Selected downloads where each one has its own section on this page.
Search
The search portlet is where constraints are added to the search query.
Filename:
Filename can be full filename like "ABC_123.dat" or some regular expression that matches a part of a filename.
Measurement date:
By default to is set to today's date and the time when the page last was refreshed and from is set to (to - 7 days).
WCUs:
This widget allows the user to filter WCUs on various search criteria. The default search criteria is 'WCU ID matches expression .*' which means that we will search on every WCU the current logged in user has access to. If the current user is an admin, we will search for all WCUs in the system. If the current user is a restricted user with access to only 10 WCUs, we will search for only those 10 WCUs.
The currently available WCU attributes to filter on is: WCU ID, Software version, Description and WCU Name
Operators:
Each search criteria has at least two operators; 'matches expression' and 'equals'.
Matches expression:
'Matches expression' means that the inserted value will be treated as a regular expression.
Equals:
'Equals means that the chosen attribute has to exactly match the inserted value.
Is one of:
For the attributes 'WCU ID' and 'WCU Name' there is an additional operator 'is one of'. When choosing this operator, the value text field is replaced by a combined search and drop down list which is populated be either all WCU IDs or WCU Names the currently logged in user has access to. One can use this operator to conveniently filter out a few WCUs where it's a non trivial task to write a regular expression that only matches the wanted wcus.
Advanced filter:
The WCUs widget allows the user build advanced nestled filters which is illustrated in the Figure "Advanced Filter".
In this example we filter "all wcus that matches expression '8' " AND "software version equals '2.43.0' " AND "description matches expression 'T20' or 'T30' ".
Cars:
This widget is very similar to the WCUs widget. Default search criteria is "Plate number matches expression .*" which basically means that we don't put any constraints on cars.
The currently available Car attributes to filter on is: Description, Plate number, Project, Proto number, Series, TSU and VIN.
Labels:
The labels section allows the user to search for result files from tasks matching the selected labels. Labels on tasks means labels that was associated with the resource (WCU or car) when the task was created. Any labels added to the resource after the task was created can not be used here. In other words, no result files for label X will be found if label X was not associated with the resource before an task was started.
File types:
The file types widget decides which file types we want to include in the search result. A file type is included in the result if the file type button in the window is toggled.
The file types 'MDF', 'TEXT' and 'VECTOR' has sub types. When toggling a button with sub types, this will enable/disable all sub types for that file type. If one only want to include a subset of the sub types, one can expand the file type and only choose the wanted sub type. If only a subset of the file sub types are selected, the file type button will be in the disabled state. If all file sub types for a file type is enabled, the file type will change to enabled state. An example can be seen in "Enable file types".
Aggregate results by:
This widget allows the user how the search results will be aggregated. Available choices are 'Day', 'Week'. 'Month' or 'Year', where 'Day' is the default option.
Results
If the search query yielded any results these results are presented as a chart in the Results portlet, an example of which can be seen in the "Search Tab" illustration above.
The X-axis depends on the chosen "Aggregate results by" in the Search portlet and the Y-axis shows the number of result files for each aggregation. The result files types that were found in the query are displayed in the legend below the chart. In the example we can see that we searched for 8 result file types but result contains 5 of them. If one clicks on any result bar in the chart a new window, "Add to download" will popup which can be seen in Figure "Add to Download". This window shows the date for the aggregation, which can be a day, a week, a month or a year, the file type (MDF in this case), the total number of files and the total size of all the files in the aggregation. The window also has a grid that shows if the aggregation consists of subsets of file sub types. In this example we only have the sub type "MDF_WITHOUT_MODULE_NAMES". When clicking the button "Add to download", this aggregation will be added to the "Selected downloads" portlet.
It is also possible to click the label of the X-axis to add all the file types for this date to "Selected downloads". In the same way it's doable to click the legend to add all found results of a particular file type to the "Selected downloads".
Selected downloads
Selected downloads shows the all aggregations added from the Results chart. An example can be seen in Figure "Selected Downloads". The columns shows basically the same information as the "Add to download" window displays before the aggregations are added for download.
Clicking "Download" starts the compilation and the user is notified when the compilation is ready for download. The compilation can take quite some time if the total file size is > 100 mb.
Save, apply and reset search criteria
In the same way as for the 'Tasks' tab and the 'Vehicles' tab, search criteria can be saved as templates. To save the current search criteria as a template, use the middle of the three buttons to the right of the Search and Cancel buttons in the Search portlets. An example of this dialogue can be seen in Figure "Save Current Search Criteria".
The leftmost button applies previously saved criteria and the rightmost buttons resets the search criteria to default.
Vehicles Tab
This view is used to handle the various vehicles that are assigned to you. A figure of this view is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you type in the criteria to be used for fetching the vehicles you are interested in. As you enter your criteria a row count is presented in the upper right area to show how many potential matches there are. The entries are also fetched as you type but only as many rows as fit your current view are fetched. As you scroll down more results will be fetched.
The number of possible columns to show is quite large. You can elect which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:
| Active alarms | Presents a numeric summary of alarms. It displays the amount of errors and warnings. |
| Connected | Shows how many minutes have passed since the WCU made a connection to the WICE portal. |
| Distance | Shows the distance the car has been driven the last week. (SoH task specific) |
| Last DRO | Says when the DRO log file was last transferred to the portal. |
| Last log | Shows when the last log file was transferred to the portal. |
| Mileage | The column shows the mileage of the car. |
| Plate number | The plate number of the car where the WCU is mounted. |
| Platform type | Search WCU by platform type. |
| Project Id | Shows the project identification number. |
| Proto number | Shows the proto number. |
| Resource group | The resource group (if any) the WCU is part of. |
| Series | Shows the series attribute. |
| TSU | Shows the TSU identifier. |
| Upload | This column says how much data has been transferred from the WCU to the portal the last week. |
| Upload date | Contains which date the last upload was done |
| Upload size | Says what the size, in kilobytes, of the last data upload was. |
| Uptime | Shows how many hours the WCU been running the last week. |
| VIN | Shows the Vehicle Identification Number of the car where the WCU is mounted. |
| Voltage | The column shows the latest known battery voltage as reported by the CEM. |
| WCU ID | The MAC ID of the WCU. For example: AA-01-AA-01-AA-01. |
| WCU Description | A textual comment attached to the WCU. |
| WCU Firmware | Shows which firmware the WCU uses. |
| WCU voltage | Shows the voltage as measured by the WCU. |
| WCU Version | Shows which version the current WCU software has. |
| WCU storage usage | Shows the amount of storage available to store data on the WCU. |
| WCU name | Shows the name of the WCU |
Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click here.
There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating tasks you can select a resource group instead of the individual WCU:s to start a new task. 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.
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu with several options, some of which are described here.
Go to Tasks Panel
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.
Go to Search Panel
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.
Go to Timeline
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.
Go to alarms
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.
Remove WCU(s) from Resource Group
If WCUs which are included in a resource group are selected, the menu option "Remove WCU(s) from Resource Group" will appear. They do not have to be in the same resource group as each other. If a resource which do not fulfill this requirement is selected in addition, this option will not be visible.
Show WCU history
Selecting this shows a window with the history of the selected WCU. In the window it can be seen when a change has been made, if there is a change in the description, if the WCU is active or not, the WCU ID, labels on the WCU, WCU Name and which user made the change. If the WCU has a modem id it will also be shown in the window. For the Show WCU history option to be available only a single WCU can be selected.
Trigger upload now
Momentarily stop the WCU, offload it and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39
Trigger reboot now
Reboots the trigger and WCU. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39
Trigger collect and upload
This action will cause the task to momentarily stop and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.45.
Trigger VIN readout
Trigger VIN readout, this action will cause the task to momentarily stop .This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.65.
New task
To create a new task for all selected WCUs, click the button New Task. To learn more about creating each specific task see Creating a Task.
Show the Vehicle Position
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in.
If you want to know more about the "Show position"-tool you can read more about it here.
View Diagnostic Trouble Codes
If an SoH task has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle. If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail. You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".
View ECU software
It is possible to see the ECU software number for each ECU in a vehicle. Press the button “ECU SW” after you have selected one vehicle. The following view will be shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with when it was read. You can download the list as a tab-separated text file if you press “Download”.
Get WCU Up-time
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
You can export data from SoH tasks 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, storage usage and diagnostic trouble codes. 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 task 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: