WICE Wiki v2.95 - User contributions [en]

Creating a Task

2021-06-23T14:19:07Z

Henrik: Added info about retention time

<includeonly>== Creating a Task==</includeonly>
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of assignment you want to create. Note that it is not possible to create a new task for a WCU which has the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU has the latter label, it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of assignments available. Remember that not all of the assignment types will be available as this depends on customer needs and some types might not be enabled in the portal.

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

== Area5 ==
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]
Area5 tasks are used to read out data from the memory of ECUs.

'''Assignment:''' To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Wizard]].

'''Validate ECU SW version on WCU:''' By checking this box, the WCU will validate that the ECU SW version of the assignment and the actual ECU are the same before starting the assignment. If they are different, it will not start the task.

'''Trigger Expression:''' The task can be started by an expression. This option lets the user specify start trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). For an explanation of trigger conditions look [[Server Trigger|here]].

'''Sync Signal:''' It is possible to specify a signal with given values that will be sent when the Area5 assignment starts and stops. This can be used to synchronize the Area5 read-out with external measurements systems like the M-Log.

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

In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero].

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

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

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

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

Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment has four options described in Figure "Canrecorder" and below:

1. In the grid, select which bus (or buses) to record from. By clicking the check box in the top left corner, you can select all buses at once.

2. Specify which CAN frames you want to record by entering their CAN IDs in the CAN frame ID column in the grid, on the same row as the bus you have selected, or by entering the IDs in the text box labeled “Set filters on selected CAN buses”. If you use the latter option, the filters will be set on all of the buses you have selected. To enter a filter on a specific bus use the method of entering the filter on the same row as the selected bus, on the grid. This can only be done if the CAN frame passthrough filter is turned on. Turning off the CAN frame passthrough filter option will disable the CAN frame ID column in the grid. Press the “Clear All” button to remove all the entered filters from all buses.

3. Turning on or off a CAN frame pass-through filter. If you choose to have the filter on you must specify which CAN bus or CAN buses you wish to record.

4. Select how long time to record before and after the trigger.

===Scheduling===

For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached.

[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]
 

To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the [[The Portal Administrator View#The Vehicles Tab|Vehicles panel]]. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.

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

== Ethernet capture ==
This kind of assignment is used to capture packet data from one of the ethernet interfaces on the WCU. The basics for this kind of assignment is that you choose the interface you would like to capture from and a capture expression to filer which packets you are interested in. The results from this assignment type is pcap files. To read more about this assignment type, go [[Ethernet capture|here]].

== IDC ==
The Internal Diagnostic Client (IDC) is a measurement module that allows a sequence of diagnostic requests to be sent and responses recorded. The sequence of diagnostic requests are uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.

== M-Log ==
The WICE system can interact with external loggers as well. One such logger is called M-Log from Ipetronik. You create your measure assignment using an external tool which creates a file which you can upload for this type of assignment. The WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.

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

== MQTT ==
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.

== Rapid prototyping ==
A Rapid prototyping (RP) task makes it possible to download RP binaries to multiple WCUs and keep track of the result files the RP assignment might produce. For more information about RP, see [[WICE RP How-To]] and [[WICE RP Manual]].
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]
The rapid prototyping tab can be seen in Figure "Rapid prototyping task".

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

== SoftHub ==
The SoftHub is a measurement system that can be run either as a stand alone unit or as a software module on the WCU, with functionality similat to the Singnal Reader module. A SoftHub task is created much in the same way as a Signal Reader task.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== SWDL ==
[[File:SWDL new task.png|thumb|791x791px|New SWDL task]]
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table.

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

SWDL tasks can optionally include one '''checksum file'''. The file is assumed to be a .xml-file. (Available from WCU version 2.66)

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

By checking the box '''Run SoH after completion''' it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.

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

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

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

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

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

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

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

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

== Applicable for all types ==
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]].

=== Site specific features ===

==== Announce result file availability ====
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]].

==== Retention time ====
[[File:Retention time.png|thumb|435x435px|Retention time]]
This function works by setting a retention time in days which simply says that data coming in from the assignment, 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 assignment 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 the default 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 default value.

File:Retention time.png

2021-06-23T14:15:57Z

Henrik:

Retention time

New features in v2.66

2021-06-23T14:09:03Z

Henrik: /* Support for retention time */

== Opportunity to not supply a measurement setup file for MLOG assignments ==
New feature while creating a [[Creating a Task#M-Log|M-Log task]].

If a measurement setup file already exists on the MLOG, it's now possible to collect generated result files in the WICE Portal without having to supply the measurement setup file.

== New information side window in vehicles panel ==
In the vehicles panel a new information window can be opened using the new icon in the bottom tool bar.

== Support to set a PIN code when clearing DTCs for SoH ==
New feature while creating a [[Creating a Task#SoH|State of Health (SoH) assignment]].

When checking the "Clear DTCs"-box it is optionally possible to enter a PIN-code for unlocking a gateway module - e.g. a Vehicle Gateway Module (VGM).

== Signal Reader assignment editor has new operand EXPR_TIMER ==
A new operand is added to the Signal Reader assignment editor called "EXPR_TIMER". Syntax is "EXPR_TIMER('expression', 'time')".

== SWDL assignment takes an optional file with software checksums ==
One optional file containing checksums can be uploaded when creating a [[Creating a Task#SWDL|SWDL task]].

The file is assumed to be a .xml-file.

== SWDL assignment can now run SoH on completion ==
It is now possible to let a [[Creating a Task#SWDL|SWDL task]] run the WCUs SoH task on SWDL completion.

== Support for retention time ==
This is only available for customers where the functionality is enabled. The function works by setting a retention time in days which simply says that data coming in from the assignment, 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 assignment to 30 days, will keep data until it is 30 days old where it will be automatically removed. Read more about it [[Creating a Task#Applicable for all types|here]].

==Ethernet Capture trigger expression and WLAN==
Ethernet capture now supports start and stop trigger expressions. Read more about it [[Ethernet capture|here.]] It also supports capturing from a WLAN interface.

== ECU List improved ==
Ecu list is improved with:
* Views for saving displayed and with of columns.
* Columns can be resized/Recorded/rescale/hided/showed
* Showing information about ECU Hardware numbers and Chassis numbers.
* For columns that contains more than one value could select displaying type:
** First value + number of
** Number of
** All value
* Timestamp for “Last known”
* Result can be exported to Excel
Read more about it [[ECU List|here.]]

2021-02-12T14:04:39Z

Henrik: Henrik uploaded a new version of File:Area5 new task.png

Area5 new task

File:Area5 new task.png

2021-02-12T13:56:58Z

Henrik:

Area5 new task

New features in v2.63

2021-02-12T13:42:30Z

Henrik: .

Creating a Task

2021-02-12T13:37:13Z

Henrik: Changed headings

<includeonly>== Creating a Task==</includeonly>
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of assignment you want to create. Note that it is not possible to create a new task for a WCU which have the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU have the latter label it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of assignments available (Canrecorder, IDC, SoH, Signal Reader, SWDL, Video, MQTT, ETAS, SoftHub and blue piraT).

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

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

Canrecorder is a measurement module that allows CAN frames to be captured and logged. This assignment has four options described in Figure "Canrecorder" and below:

1. In the grid, select which bus (or buses) to record from. By clicking the check box in the top left corner, you can select all buses at once.

2. Specify which CAN frames you want to record by entering their CAN IDs in the CAN frame ID column in the grid, on the same row as the bus you have selected, or by entering the IDs in the text box labeled “Set filters on selected CAN buses”. If you use the latter option, the filters will be set on all of the buses you have selected. To enter a filter on a specific bus use the method of entering the filter on the same row as the selected bus, on the grid. This can only be done if the CAN frame passthrough filter is turned on. Turning off the CAN frame passthrough filter option will disable the CAN frame ID column in the grid. Press the “Clear All” button to remove all the entered filters from all buses.

3. Turning on or off a CAN frame pass-through filter. If you choose to have the filter on you must specify which CAN bus or CAN buses you wish to record.

4. Select how long time to record before and after the trigger.

===Scheduling===

For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached.

[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]
 

To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the [[The Portal Administrator View#The Vehicles Tab|Vehicles panel]]. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.

== IDC ==
The Internal Diagnostic Client (IDC) is a measurement module that allows a sequence of diagnostic requests to be sent and responses recorded. The sequence of diagnostic requests are uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.

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

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

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

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

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

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

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

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

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

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

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

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

=== WICE internal signals ===
In addition to CAN and FlexRay signals, a number of internal signals are also available. The following WICE-internal signals are supported:
{| class="wikitable"
!'''Signal name'''
!Description
|-
|Accelerometer_X
|The value of the X direction of the WCU's built-in accelerometer.
|-
|Accelerometer_Y
|The value of the Y direction of the WCU's built-in accelerometer.
|-
|Accelerometer_Z
|The value of the Z direction of the WCU's built-in accelerometer.
|-
|Audio_Device_1
|The status of audio device 1 (1=recording, 0 = not recording). When present in a recorder, the audio module will record sound from the device.
|-
|Audio_Device_2
|The status of audio device 2 (1=recording, 0 = not recording). When present in a recorder, the audio module will record sound from the device.
|-
|Busload_CAN_<n>
|The bus load on CAN bus <n>
|-
|CSQ
|The built-in modem's CSQ value (Signal Quality)
|-
|Date_Year
|The year of the current date.
|-
|Date_Month
|The month (1-12) of the current date.
|-
|Date_Day
|The day of the month (1-31) of the current date.
|-
|Date_Weekday
|The day of the week (1-7, where 1 is Sunday).
|-
|Date_Hour
|The hour of the day (0-23).
|-
|Date_Minute
|The minute of the hour (0-59).
|-
|Date_Second
|The second of the minute (0-59).
|-
|Dynamic_<n>
|Special signals with values assignable from external software components (typically used for Rapid Prototyping).
|-
|IO__AI_<n>
|Analog input number <n>
|-
|IO__DI_<n>
|Digital input number <n>
|-
|IO__DO_<n>
|Digital output number <n>
|-
|Log_All_Frames_CAN_<n>
|Log all CAN frames on CAN bus <n>
|-
|Log_All_Frames_FlexRay_<n>
|Log all CAN frames on Flexray bus <n>
|-
|Latitude
|The GPS latitude
|-
|Longitude
|The GPS longitude
|-
|Power_Mode
|The power mode of the WCU
|-
|Random
|A random number generator
|-
|Random_Start
|A random number generator updated once, at program start
|-
|Random_Setup_Switch
|A random number generator updated at each measurement set-up switch
|-
|Start_Signal
|The start signal of the WCU
|-
|Speed
|The GPS speed
|-
|Start_Switch
|The start switch of the WCU
|-
|Tester_Present
|When present in a measurement set-up, a Tester Present diagnostic request (with suppress Positive Response bit set) will be sent periodically.
|-
|Time_Since_Epoch
|The time elapsed since the epoch (Jan 1, 1970, 00:00)
|-
|Time_Since_Start
|The time elapsed since the start of the assignment
|-
|Time_Since_Setup Switch
|The time elapsed since the activation of the current measurement set-up
|-
|Trigger_Button
|The trigger button connected to the WCU
|-
|Usage_CPU
|The WCU CPU usage in percent
|-
|Usage_Memory
|The WCU memory usage in percent
|-
|Video_Camera_1
|The status of video camera 1 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.
|-
|Video_Camera_2
|The status of video camera 2 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.
|-
|WCU_Battery
|The WCU battery voltage in millivolts
|-
|WCU_Temp
|The WCU internal temperature in degrees Celsius
|-
|WCU_Voltage
|The WCU WCU voltage in millivolts
|}
 

== SWDL ==
[[File:SWDL new task.png|thumb|791x791px|New SWDL task]]
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table.

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

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

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

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

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

== ETAS ==
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.

When creating an ETAS task, the assignment description file you select must be a .exp file.

== SoftHub ==
The SoftHub is a measurement system that can be run either as a stand alone unit or as a software module on the WCU, with functionality similat to the Singnal Reader module. A SoftHub task is created much in the same way as a Signal Reader task.

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

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

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

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

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

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

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

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

== MQTT ==
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.

== Rapid prototyping ==
A Rapid prototyping (RP) task makes it possible to download RP binaries to multiple WCUs and keep track of the result files the RP assignment might produce. For more information about RP, see [[WICE RP How-To]] and [[WICE RP Manual]].
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]
The rapid prototyping tab can be seen in Figure "Rapid prototyping task".

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

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

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

A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.
[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero].

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

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

New features in v2.63

2021-02-12T13:33:20Z

Henrik: Added Area5 New Task Trigger and Sync

New features in v2.61

2020-12-08T09:20:13Z

Henrik: Added Validation of ECU SW version

==A2L File version and ECU bind==
New features have been added that allows setting of A2L file version and binding the file to an ECU on upload. The version can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU. It is also possible to add multiple A2L files per ECU in Vehicle Profile now! Read more [[Vehicle Pofiles|here]].

== Area5 ==
Area5 is finally handled by Wice! It comes complete with an [[Area5 Assignment Wizard|assignment creator]] and ability to create tasks from created assignments.

== Signal Reader Assignment Wizard Choose A2L file ==
It is now possible to choose which A2L file to use per ECU when creating a [[Signal Reader Assignment Wizard|Signal Reader Assignment]].

== Validation of ECU SW version ==
ECU SW version is now validated in new task. When creating a new task for signal reader and area5 while using saved assignments, the ECU SW version on WCUs are validated against the A2L file/ECU SW versions used in the assignment. This validation requires that the WCU's vehicle has a designated diagnostic file and that ECU SW versions has been read from the vehicle through a SoH task.

There is also now a checkbox in the task creator to perform the same validation, but on the WCU, before the task is run.

Signal Reader Assignment Wizard

2020-12-08T09:02:27Z

Henrik: Added Choose A2L file per ECU popup description

<includeonly>=Assignment Tab=</includeonly>

The Signal Reader Assignment Wizard, also known as '''haf creator''', can be found under the tab '''Assignment''' and allows the user to create new assignments for signal reader directly on the portal. This page will guide you through the basics of using the wizard.
== Choosing a Signal Source ==
First, you must select a signal source to base your new assignment on. Today, only custom vehicle types can be used for this, see Figure "Choosing a Signal Source". If you would like to edit the Custom Vehicle types or create a new one, this can be done by admins under the administration tab.

When you feel comfortable with which signal source you would like to use, double click it or select it and click '''Create new assignment'''.[[File:Choose Signal Source.png|thumb|Choosing a Signal Source|600x600px|none]]In case the chosen Vehicle Profile has multiple A2L files per ECU a prompt will show up where it is possible to choose which A2L file to use per ECU. If no A2L file is chosen, that ECU is not used when creating the assignment.
[[File:SignalReaderChooseA2LFilePerECU.png|none|thumb|Choose A2L File Per ECU Popup]]

== Creating a new assignment ==
Now that you have chosen a signal source, you can start creating the assignment. The first tab that you are presented with is the '''Assignment global settings''' tab where you can add information about the assignment so that you can easily keep track of what this assignment is about. Creator and creation date are both automatically filled in and cannot be changed because of consistency.
[[File:MeasurementSetup2.png|thumb|600x600px|Measurement Setups]]
[[File:Edit-DAQ2.png|thumb|600x600px|Edit DAQ]]
Under the '''Measurements''' tab, see Figure "Measurement Setups", you are presented to a table of Measurement Setups and an information window. These measurement setups are the core of a signal reader assignment. They contain '''Triggers''' that activate and deactivate on certain conditions provided by the user. Each trigger can contain a '''Recorder''' that contains a list of certain signals that will be measured when the start condition for the respective trigger is met. A trigger can also be used to act as a '''setup switch'''.

Measurement setups keep track of the signals that are present in them, as seen in Figure "Measurement Setups". If a CCP signal is present in the measurement setup it is possible to assign it to an individual '''DAQ list''' by pressing Edit DAQ. This brings up the window in Figure "Edit DAQ". Here you can drag and drop signals to the corresponding DAQ list that you which them to be in.

When you feel finished with the assignment you can simply click the '''Save assignment''' button in the lower right corner to save the assignment in its current state.

=== Trigger ===
To add a trigger to a measurement setup, click the '''Add trigger''' button for the respective measurement setup. This will create a new Trigger in the trigger table in the respective measurement setup and the information window will be filled with new settings for this trigger for you to add.

Fill out the '''start trigger''' '''condition''' for the trigger. This is easiest to do in the '''Edit expression''' window that you can get to by clicking one of the '''Edit''' buttons. To find a new signal to add a condition for, use the '''Add signal''' button. Here, you can browse all signals available for this assignment. Use the dropdown to browse signals from different can-busses and Wice generic internal signals. If you want to browse the signals currently in use in the assignment for the selected signal source, check the '''Search in assignment''' box. If you want more information about a signal, select it and click '''More info'''. When you have found the signal you want, double click it or select it and click '''Add signal'''. Now you can use the '''Operators''' list to add a condition for the signal, for example " > 0". When you are satisfied with the start condition, you will notice that the Validate button has a yellow warning symbol on it. This means that the expression is unvalidated, press the button to validate the expression. The buttons icon now either turns red (expression is unvalid) or green (expression is correct). See Figure "Validate Button States" for the different state of the validate button. Click Save to save the expression. The list of operators supported in trigger condition is available [[Signal Reader Trigger Expressions|here]].

[[File:ValidateButtonStates.png|thumb|Validate Button States]]

A '''stop trigger condition''' is not required, but can be supplied to determine when the recording should stop. If the stop condition is not supplied, the settings for the recorder will tell when the recording should stop.

You can use the '''trigger''' '''Setup switch''' to switch to/run a measurement setup when the start condition is met. Keep in mind though, that the setup switch will not run until all currently started recorders have at least fulfilled their '''minimum duration'''. A trigger with a recorder cannot have a setup switch, but the recorder can.

=== Recorder ===
There a two types of recorder, SREC (Signal recorder) and DREC (Diagnostics recorder). Choose which one you want with the radio button at the top of the Recorder tab.

===== Recorder - DREC =====
DREC (Diagnostics recorder) is used to ask diagnostic questions on the buses and record the answers. The questions to ask are determined by a sequence file that you are asked to upload.

==== Recorder - SREC ====
SREC (Signal recorder) is used to record signals on the busses.
[[File:AddSignalsRecorder.png|thumb|600x600px|Add Signals for Recorder]]
[[File:ImportSignalsText2.png|thumb|559x559px|Import signals from text]]

===== SREC - Signals =====
Click the '''Add Signal''' button to open a window to add signals for recording. This window is much like the window for adding signals for the trigger, only differing in the fact that you can select multiple signals in this window. The selected signals for this recorder are shown in the right table, see Figure "Add Signals for Recorder". To add new signals to this table, you can either:
* Double click the signal,
* Drag and drop the signal
* Select the signal and click the right pointing arrow
Click the red symbol to the right of each signal to remove it. When you are done, click Ok to add the signals.

It is also possible to '''import''' signals from a text file or directly from text as well as '''export''' signals as text. To do this, use the corresponding icon in the bottom right corner of the "Selected Symbols" list as senn in Figure "Add Signals for Recorder". The figure "Import signals from text" gives an example on how the text file and text is expected to be structured when importing signals. Each line is expected to be a signal, with or without the module name. If the signal does not have a module name it is expected to belong to the already selected signal source/module. When importing CCP signals it is here possible to select which DAQ list that all found CCP signals should be assigned to, using the drop down.

Now that you have added some signals, you can give them each a '''Skip factor''', default 1, which is an integer that determines how often the signal should be recorded/stored when supplied. For example, a skip factor of 1 will record the signal every time it is supplied and a skip factor of 3 will record the signal every third sample.

===== Recorder - Properties =====
Under the recorder tab '''Properties''' you can select the properties for the recorder, see Figure "Recorder Properties".

'''Number of shots''' is an important factor for a recorder. A '''shot''' is the term used for a single recording and number of shots is therefore the number of times we should record. A shot is only started when the start trigger condition is met and will continue until any of these events occur:
* The recording fulfills the maximum duration.
* The recording fulfills the minimum duration and the '''stop trigger condition''' is met.
* The recording fulfills the minimum duration and a trigger start a '''setup switch'''.
* The recording fulfills the minimum duration and another recorder starts a '''setup switch'''.
* A setup switch is started manually.
* The assignment is stopped manually.
The '''recorder Setup switch''' is started when recorder has performed its number of shots and all other started recorders have at least fulfilled their minimum duration. It is, like the trigger setup switch, used to switch to/run a measurement setup.

You can also select the '''Pre trigg duration''' which determines the amount of data that will be saved in the flash before the start trigger condition is met. Range is 0 to 4294967295 (232).

The '''Post trigg duration''' is much like the pre trigg duration and determines the amount of data that will be saved after the stop trigger condition is met. Range is 0 to 4294967295 (232).

The '''Minimum duration''' determines the minimum amount of data that needs to be recorded before it becomes possible to cancel the recording through either a stop trigger or a setup swtich started by a trigger or another recorder.

The '''Maximum duration''' determines, as the name suggest, the maximum amount of data that should be recorded. Range is 0 to 4294967295 (232).

The '''Unit''' for the four aforementioned durations can be set to seconds, samples or bytes. If you choose to set them to seconds, the device will use the timestamps of the incoming data to determine the four aforementioned durations.[[File:Recorder properties.png|thumb|600x600px|Recorder Properties|none]][[File:View assignments.png|thumb|600x600px|View Assignments]]

== Editing an assignment ==
In order to edit an already created assignment navigate to the tab where you choose a signal source and click the '''View saved assignments''' button. This will display a window, see Figure "View Assignments", which lists all of the saved assignments created through the wizard, by whom and when it was created. In order to edit an assignment, select it and click '''Edit''' and you will start editing it. Simply click '''Save assignment''' when you are done and the old version of the assignment will be updated.

== Using a portal assignment for a signal reader task ==
In order to use a portal assignment. Select the WCUs in the Vehicle tab that you want to create the new signal reader assignment for and click new task. Navigate to the Signal reader tab and click the '''Browse saved assignments''' button and select the assignment you want to use and click '''Ok'''. This assignment will now be used to create the .haf file required by the WCUs to perform the signal reader task.

File:SignalReaderChooseA2LFilePerECU.png

2020-12-08T08:59:41Z

Henrik:

SignalReaderChooseA2LFilePerECU

New features in v2.61

2020-12-08T08:53:57Z

Henrik: Added Signal Reader ECU update

Area5 Assignment Wizard

2020-12-08T08:51:30Z

Henrik: Added Images

The Area5 Assignment Wizard can be found under the '''Assignment''' tab and allows the user to create new assignments for area5 directly on the portal. This page will guide you through the basics of using the wizard.

== Choosing a Signal Source ==
Choose a Vehicle Profile to base the area5 assignment on and click '''create new assignment''' in the bottom right, or simply double click the vehicle profile.

If the selected Vehicle Profile has multiple A2L-files per ECU, a prompt will pop up where it is possible to choose which A2L-file to use per ECU. It is also possible to leave ECUs without a file, the ECU will then simply not be used in this assignment. See Figure 1.
[[File:Area5SelectA2LFilePerECU.png|none|thumb|Figure 1: Select A2L file per ECU]]

== Creating a new assignment ==
In the top, you can specify the name of the assignment.
[[File:Area5AssignmentWizard.png|none|thumb|400x400px|Figure 2: Area5 assignment]]

=== Choosing Memory Segment ===
When a signal source has been chosen, the view in figure 2 is displayed. Here, all available memory segments are listed, grouped by ECU and A2L file. To choose a memory segment to measure, simply click its row and make sure its checkbox is checked.

=== Save ===
Save the assignment by clicking '''Save Assignment''' in the bottom right.

== Browse saved assignments ==
You can browse saved assignments by clicking '''Browse saved area5 assignments''' in the top left of the panel where you choose a signal source.

File:Area5AssignmentWizard.png

2020-12-08T08:49:18Z

Henrik:

Area5AssignmentWizard

File:Area5SelectA2LFilePerECU.png

2020-12-08T08:43:41Z

Henrik:

Area5SelectA2LFilePerECU

Area5 Assignment Wizard

2020-12-08T08:27:40Z

Henrik: Added Creating a new assignment

The Area5 Assignment Wizard can be found under the '''Assignment''' tab and allows the user to create new assignments for area5 directly on the portal. This page will guide you through the basics of using the wizard.

== Choosing a Signal Source ==
Choose a Vehicle Profile to base the area5 assignment on and click '''create new assignment''' in the bottom right, or simply double click the vehicle profile.

If the selected Vehicle Profile has multiple A2L-files per ECU, a prompt will pop up where it is possible to choose which A2L-file to use per ECU. It is also possible to leave ECUs without a file, the ECU will then simply not be used in this assignment.

== Creating a new assignment ==
In the top, you can specify the name of the assignment.

=== Choosing Memory Segment ===
When a signal source has been chosen, the view in figure 2 is displayed. Here, all available memory segments are listed, grouped by ECU and A2L file. To choose a memory segment to measure, simply click its row and make sure its checkbox is checked.

=== Save ===
Save the assignment by clicking '''Save Assignment''' in the bottom right.

== Browse saved assignments ==
You can browse saved assignments by clicking '''Browse saved area5 assignments''' in the top left of the panel where you choose a signal source.

New features in v2.61

2020-12-08T08:08:35Z

Henrik: Added Area5

Area5 Assignment Wizard

2020-12-08T08:07:53Z

Henrik: Added Choosing signal source

New features in v2.61

2020-12-07T16:26:21Z

Henrik:

Vehicle Profiles

2020-12-07T16:18:40Z

Henrik: Added text about adding new ECU

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "vehicle profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]] 
== Manage Description files ==
The "Bus description files" portlet let the user upload, change or remove description files. These files are used to describe the interfaces. Currently, the descriptiojn files taht are supported are DBC for CAN, FIBEX for Flexrasy and A2L for ECU.

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

File:AddNewECU.png

2020-12-07T16:12:55Z

Henrik:

AddNewECU

Vehicle Profiles

2020-12-07T16:10:30Z

Henrik: Added upload A2L file

[[File:VehicleProfiles.png|thumb|1000x1000px|Vehicle Profiles Panel]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "vehicle profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. They are defined by A2L files and it is possible to add a seed/key to them individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential. See image "Edit ECU".
[[File:SeedKey.png|none|thumb|Edit Seed/key]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]] 
== Manage Description files ==
The "Bus description files" portlet let the user upload, change or remove description files. These files are used to describe the interfaces. Currently, the descriptiojn files taht are supported are DBC for CAN, FIBEX for Flexrasy and A2L for ECU.

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

File:UploadNewA2lFile.png

2020-12-07T16:02:52Z

Henrik:

UploadNewA2lFile