<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.alkit.se/wice299/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mathias</id>
	<title>WICE Wiki v2.99 - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.alkit.se/wice299/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Mathias"/>
	<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php/Special:Contributions/Mathias"/>
	<updated>2026-11-16T17:05:36Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.44.0</generator>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4262</id>
		<title>Creating a Task</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4262"/>
		<updated>2026-09-22T11:37:17Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* User Defined signals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;includeonly&amp;gt;== Creating a Task==&amp;lt;/includeonly&amp;gt;&lt;br /&gt;
You create a new task by pressing the &amp;quot;New Task&amp;quot; button on the bottom of the &amp;quot;Tasks&amp;quot; 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 &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_in_progress&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt; or &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_done&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;. 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. &lt;br /&gt;
&lt;br /&gt;
To learn about how to add resources to the task, check [[New task|here]].&lt;br /&gt;
&lt;br /&gt;
== Arcos ==&lt;br /&gt;
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]&lt;br /&gt;
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 &amp;quot;&#039;&#039;.ccmc&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the Arcos - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== Area5 ==&lt;br /&gt;
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]&lt;br /&gt;
Area5 tasks are used to read out data from the memory of ECUs. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Assignment:&#039;&#039;&#039; To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Validate ECU SW version on WCU:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Trigger Expression:&#039;&#039;&#039; 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]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Sync Signal:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
== Audio ==&lt;br /&gt;
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader &#039;&#039;&#039;recorder&#039;&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;Audio level&#039;&#039;&#039;: Start the trigger once the microphone registers volume above a certain threshold.&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible.&lt;br /&gt;
  &lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let&#039;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 &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
It is possible to monitor the audio live. To do this, check the box &amp;quot;Monitoring&amp;quot;. To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. &lt;br /&gt;
&lt;br /&gt;
There is more information about audio in WICE [[Wice audio|here]].&lt;br /&gt;
&lt;br /&gt;
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== Blue piraT ==&lt;br /&gt;
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 &amp;quot;extra bundle&amp;quot;). Contact Alkit Communications in order to set this up.&lt;br /&gt;
&lt;br /&gt;
== CAN-recorder ==&lt;br /&gt;
[[File:Canrecorder.png|thumb|Canrecorder]]&lt;br /&gt;
Canrecorder is a measurement module that allows CAN frames to be captured and logged.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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”&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Scheduling=== &lt;br /&gt;
&lt;br /&gt;
For WCUs with version &amp;gt;= 2.53 this task can be scheduled by selecting the &amp;quot;Add schedule&amp;quot;-checkbox. By doing so, the panel shown in Figure &amp;quot;Schedule Panel&amp;quot; appears. By thereafter selecting the &amp;quot;ASAP&amp;quot; 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 &amp;quot;Time span&amp;quot; and &amp;quot;Repeat&amp;quot;-checkboxes and select the sought time in the &amp;quot;Start field&amp;quot;. The task can also be performed within a certain time span, and in this case &amp;quot;Time span&amp;quot; should be checked and the Date in &amp;quot;End&amp;quot; field specified. Repetition of the task is defined by checking the &amp;quot;Repeat&amp;quot; checkbox, defining a interval size in the field after &amp;quot;Every&amp;quot; and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the &amp;quot;Until&amp;quot; field is reached. By selecting the &amp;quot;On ignition&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]&lt;br /&gt;
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with &#039;On ignition&#039; enabled]]&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To control the time zone in which the task scheduling is to be performed the &amp;quot;WCU local time&amp;quot;-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 &amp;gt;= 2.53 by an administrator using &amp;quot;Edit configuration&amp;quot; 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 &amp;quot;WCU local time&amp;quot;-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.&lt;br /&gt;
&lt;br /&gt;
== Diagnostic Log and Trace (DLT) ==&lt;br /&gt;
The DLT functionality comes in two flavors. One is based on communicating with a DLT daemon on the ECU and the other is based on the UDS service 38. You switch between the using the button &amp;quot;DLT UDS mode&amp;quot;. &lt;br /&gt;
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]&lt;br /&gt;
From version 2.96 it also possible to create a task with DLT daemon and DLT UDS mode enabled at the same time by checking the &amp;quot;Enable multi task&amp;quot; checkbox as can be seen in the screenshot the right. &lt;br /&gt;
&lt;br /&gt;
=== DLT Daemon Mode ===&lt;br /&gt;
DLT itself provides a log and trace interface, based on the standardized 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 [https://github.com/GENIVI/dlt-daemon here]. &lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:&lt;br /&gt;
&lt;br /&gt;
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check &amp;quot;Use vehicle announcement&amp;quot; (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.&lt;br /&gt;
# Daemon port - which port on the address the daemon is at.&lt;br /&gt;
# 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 [https://github.com/GENIVI/dlt-daemon#learn-more here].&lt;br /&gt;
&lt;br /&gt;
=== DLT UDS Mode ===&lt;br /&gt;
When in this mode the user is presented with a list of directories to handle. Each row in the table is for a specific WCU and directory, as indicated in the illustration for the UDS mode to the right. To add a row, or directory to fetch, press the button &amp;quot;Add transfer&amp;quot;. An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number and the directory to fetch. You may also choose service area for the transfer, with the default being 0x19. You can add as many entries as you wish.&lt;br /&gt;
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]&lt;br /&gt;
Previously it was possible to manually enter a PIN, that is no longer possible. Instead PINs will be automatically applied if they are available in the portal. For each transfer the specified ECU and area are used to find the correct PIN. For this to be possible PINs must either have been [[Vehicles#Upload Vehicle pins|uploaded from file]] or [[The Portal Administrator View#The Resource Groups Tab|fetched from PIE]].&lt;br /&gt;
&lt;br /&gt;
There is also a button &amp;quot;Check PINs&amp;quot; that will either show which ECUs and areas have PINs available for the vehicle if it is a WCU, or if it is a resource group show which resources have missing PINs.&lt;br /&gt;
&lt;br /&gt;
== ETAS ==&lt;br /&gt;
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
When creating an ETAS task, the task description file you select must be a .exp file.&lt;br /&gt;
&lt;br /&gt;
== Ethernet capture ==&lt;br /&gt;
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 [[Ethernet capture|here]].&lt;br /&gt;
&lt;br /&gt;
== File fetcher ==&lt;br /&gt;
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]&lt;br /&gt;
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.&lt;br /&gt;
&lt;br /&gt;
The following needs to be specified when creating such a task:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;File path&#039;&#039;&#039; - One or several paths to a files or file-containing directories on the unit&#039;s file system. This specifies which files that will be fetched.&lt;br /&gt;
* &#039;&#039;&#039;Username&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;Password&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;IP address&#039;&#039;&#039; - To find the unit.&lt;br /&gt;
* &#039;&#039;&#039;Port&#039;&#039;&#039; -  To find the unit. Default is 22, but can be changed.&lt;br /&gt;
&lt;br /&gt;
Furthermore, the task also allows the use of a proxy.&lt;br /&gt;
&lt;br /&gt;
To use a proxy, the &#039;&#039;&#039;Use Proxy&#039;&#039;&#039; checkbox has to be checked, and the following must be specified:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Proxy Username&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Password&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy IP Address&#039;&#039;&#039; - To find the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Port&#039;&#039;&#039; - To find the proxy unit. Default is 22, but can be changed.&amp;lt;br /&amp;gt;&lt;br /&gt;
== IDC ==&lt;br /&gt;
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 &amp;quot;.seq&amp;quot;). This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== IPEmotion RT ==&lt;br /&gt;
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 &amp;quot;&#039;&#039;.irf&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== LPD ==&lt;br /&gt;
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.&lt;br /&gt;
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]&lt;br /&gt;
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]&lt;br /&gt;
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 &amp;quot;Edit&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
== M-Log ==&lt;br /&gt;
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.[[File:MlogForWiki.png|thumb|M-Log task]]&lt;br /&gt;
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the MLOG - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
==== Software version validation (Available from version 2.74.0) ====&lt;br /&gt;
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|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. &lt;br /&gt;
&lt;br /&gt;
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|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 &amp;quot;Add&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
A negative validation is 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 &amp;quot;Submit&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
If any ECU software versions have changed during the course of running the task it is also possible to edit the task in order to add, edit, or remove ECU SW to be validated anew. &lt;br /&gt;
 &lt;br /&gt;
== MQTT ==&lt;br /&gt;
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.&lt;br /&gt;
&lt;br /&gt;
== Rapid prototyping ==&lt;br /&gt;
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]].&lt;br /&gt;
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]&lt;br /&gt;
The rapid prototyping tab can be seen in Figure &amp;quot;Rapid prototyping task&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
An RP task must consist of at least an &#039;RP binary&#039; or a &#039;Web application zip file&#039;.&lt;br /&gt;
&lt;br /&gt;
== SoftHub ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. &lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;server triggers&#039;&#039;&#039; to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader == &lt;br /&gt;
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]&lt;br /&gt;
Signal Reader is a data capture module that allows monitoring and logging of CAN, LIN 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:&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Chosen file&amp;quot; field.&lt;br /&gt;
&lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting &amp;quot;Monitor signals&amp;quot;. 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 &#039;&#039;&#039;Monitor Signals&#039;&#039;&#039; 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&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;Server Triggers&#039;&#039;&#039; to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
=== The Signal Broker === &lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
=== Files containing references to sequence files === &lt;br /&gt;
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] &lt;br /&gt;
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 &#039;&#039;Snapshots&#039;&#039; or &#039;&#039;Extended data&#039;&#039;. An example of this can found in Figure &amp;quot;Sequence Files References in .haf File&amp;quot;. &lt;br /&gt;
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] &lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Sequence File with Functional Query&amp;quot; we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read &#039;&#039;Extended data&#039;&#039;. It is also possible to select both &#039;&#039;Snapshots&#039;&#039; and &#039;&#039;Extended data&#039;&#039;.  &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== WICE internal signals ===&lt;br /&gt;
In addition to CAN and other 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]]&lt;br /&gt;
&lt;br /&gt;
=== User Defined signals ===&lt;br /&gt;
You can define new signals by combining signals using [[Logical expressions]], [[Arithmetic expressions]] and [[Special expressions]]. The user defined signals can be recorded and can be used in Trigger expressions.&lt;br /&gt;
&lt;br /&gt;
== SoH ==&lt;br /&gt;
[[File:SoH.png|thumb|799x799px|SoH]]&lt;br /&gt;
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 &amp;quot;SoH&amp;quot;. 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_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:&lt;br /&gt;
*Mileage&lt;br /&gt;
*Voltage&lt;br /&gt;
*Read ECU software numbers&lt;br /&gt;
*Read ECU DTC:s (optionally including &#039;Snapshot&#039; and &#039;Extended data&#039;)&lt;br /&gt;
*Read OBD-II PIDs&lt;br /&gt;
*App Diagnotstic Db Part Num&lt;br /&gt;
*Build ID&lt;br /&gt;
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]&lt;br /&gt;
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)&lt;br /&gt;
*Clear DTCs. &lt;br /&gt;
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)&lt;br /&gt;
**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)&lt;br /&gt;
*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 task. It is a text type of file. In addition, a system value label called &#039;engine_hours&#039; (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle.  &lt;br /&gt;
&lt;br /&gt;
This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
Some selections above might not be available to you as this is a configuration setting depending on customer.&lt;br /&gt;
&lt;br /&gt;
== SWDL ==&lt;br /&gt;
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]&lt;br /&gt;
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. &amp;lt;code&amp;gt;ff:00:1a:2c:77&amp;lt;/code&amp;gt; (or alternatively, omitting the colon separator, &amp;lt;code&amp;gt;ff001a2c77&amp;lt;/code&amp;gt;). 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 &amp;quot;New SWDL task&amp;quot;. To get an overview of how the files relate to the ECUs it is possible to choose the &amp;quot;Group by&amp;quot;-option when right clicking the ECU column in the file table. &lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;pre-update sequence file and/or a post-update sequence file&#039;&#039;&#039;. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include one &#039;&#039;&#039;signature file&#039;&#039;&#039; (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)&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;VGM unlock&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
By checking the box &#039;&#039;&#039;Run SoH after completion&#039;&#039;&#039; it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.&lt;br /&gt;
&lt;br /&gt;
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box &amp;quot;&#039;&#039;&#039;Use Vehicle Pin mappings&#039;&#039;&#039;&amp;quot;. 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 [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally contain a &#039;&#039;&#039;Trigger Expression&#039;&#039;&#039; which must be fulfilled within a specified time limit (&amp;quot;Wait time&amp;quot;) 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.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
It is also possible to choose to &#039;&#039;&#039;ignore checksums&#039;&#039;&#039; and/or &#039;&#039;&#039;disable pre-programming&#039;&#039;&#039; using the corresponding checkboxes.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
== Video ==&lt;br /&gt;
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:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: To initiate the recording you need to attach a button to the WCU in order to start in the video recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader &#039;&#039;recorder&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)&lt;br /&gt;
&lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time (not valid in the cases of the &#039;None&#039; trigger option above). As an example, let&#039;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.&lt;br /&gt;
&lt;br /&gt;
A maximum &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Read more about the video support in WICE [[WICE_video|here]].&lt;br /&gt;
&lt;br /&gt;
== Applicable for all types ==&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]].&lt;br /&gt;
&lt;br /&gt;
=== Site specific features ===&lt;br /&gt;
&lt;br /&gt;
==== Announce result file availability ====&lt;br /&gt;
[[File:Resultfilepanel.png|thumb|Announced On column]]&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there&#039;s a new &#039;Announced On&#039; column that keeps track of when the result file was announced.&lt;br /&gt;
&lt;br /&gt;
==== Retention time ====&lt;br /&gt;
[[File:Retention time.png|thumb|435x435px|Retention time]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
It is possible to set a default retention time for resource groups. To do this, add a global value label named &#039;&#039;&#039;RETENTION_TIME&#039;&#039;&#039; 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.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4261</id>
		<title>Creating a Task</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4261"/>
		<updated>2026-09-22T11:36:19Z</updated>

		<summary type="html">&lt;p&gt;Mathias: UD signals&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;includeonly&amp;gt;== Creating a Task==&amp;lt;/includeonly&amp;gt;&lt;br /&gt;
You create a new task by pressing the &amp;quot;New Task&amp;quot; button on the bottom of the &amp;quot;Tasks&amp;quot; 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 &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_in_progress&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt; or &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_done&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;. 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. &lt;br /&gt;
&lt;br /&gt;
To learn about how to add resources to the task, check [[New task|here]].&lt;br /&gt;
&lt;br /&gt;
== Arcos ==&lt;br /&gt;
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]&lt;br /&gt;
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 &amp;quot;&#039;&#039;.ccmc&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the Arcos - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== Area5 ==&lt;br /&gt;
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]&lt;br /&gt;
Area5 tasks are used to read out data from the memory of ECUs. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Assignment:&#039;&#039;&#039; To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Validate ECU SW version on WCU:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Trigger Expression:&#039;&#039;&#039; 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]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Sync Signal:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
== Audio ==&lt;br /&gt;
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader &#039;&#039;&#039;recorder&#039;&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;Audio level&#039;&#039;&#039;: Start the trigger once the microphone registers volume above a certain threshold.&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible.&lt;br /&gt;
  &lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let&#039;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 &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
It is possible to monitor the audio live. To do this, check the box &amp;quot;Monitoring&amp;quot;. To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. &lt;br /&gt;
&lt;br /&gt;
There is more information about audio in WICE [[Wice audio|here]].&lt;br /&gt;
&lt;br /&gt;
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== Blue piraT ==&lt;br /&gt;
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 &amp;quot;extra bundle&amp;quot;). Contact Alkit Communications in order to set this up.&lt;br /&gt;
&lt;br /&gt;
== CAN-recorder ==&lt;br /&gt;
[[File:Canrecorder.png|thumb|Canrecorder]]&lt;br /&gt;
Canrecorder is a measurement module that allows CAN frames to be captured and logged.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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”&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Scheduling=== &lt;br /&gt;
&lt;br /&gt;
For WCUs with version &amp;gt;= 2.53 this task can be scheduled by selecting the &amp;quot;Add schedule&amp;quot;-checkbox. By doing so, the panel shown in Figure &amp;quot;Schedule Panel&amp;quot; appears. By thereafter selecting the &amp;quot;ASAP&amp;quot; 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 &amp;quot;Time span&amp;quot; and &amp;quot;Repeat&amp;quot;-checkboxes and select the sought time in the &amp;quot;Start field&amp;quot;. The task can also be performed within a certain time span, and in this case &amp;quot;Time span&amp;quot; should be checked and the Date in &amp;quot;End&amp;quot; field specified. Repetition of the task is defined by checking the &amp;quot;Repeat&amp;quot; checkbox, defining a interval size in the field after &amp;quot;Every&amp;quot; and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the &amp;quot;Until&amp;quot; field is reached. By selecting the &amp;quot;On ignition&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]&lt;br /&gt;
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with &#039;On ignition&#039; enabled]]&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To control the time zone in which the task scheduling is to be performed the &amp;quot;WCU local time&amp;quot;-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 &amp;gt;= 2.53 by an administrator using &amp;quot;Edit configuration&amp;quot; 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 &amp;quot;WCU local time&amp;quot;-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.&lt;br /&gt;
&lt;br /&gt;
== Diagnostic Log and Trace (DLT) ==&lt;br /&gt;
The DLT functionality comes in two flavors. One is based on communicating with a DLT daemon on the ECU and the other is based on the UDS service 38. You switch between the using the button &amp;quot;DLT UDS mode&amp;quot;. &lt;br /&gt;
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]&lt;br /&gt;
From version 2.96 it also possible to create a task with DLT daemon and DLT UDS mode enabled at the same time by checking the &amp;quot;Enable multi task&amp;quot; checkbox as can be seen in the screenshot the right. &lt;br /&gt;
&lt;br /&gt;
=== DLT Daemon Mode ===&lt;br /&gt;
DLT itself provides a log and trace interface, based on the standardized 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 [https://github.com/GENIVI/dlt-daemon here]. &lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:&lt;br /&gt;
&lt;br /&gt;
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check &amp;quot;Use vehicle announcement&amp;quot; (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.&lt;br /&gt;
# Daemon port - which port on the address the daemon is at.&lt;br /&gt;
# 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 [https://github.com/GENIVI/dlt-daemon#learn-more here].&lt;br /&gt;
&lt;br /&gt;
=== DLT UDS Mode ===&lt;br /&gt;
When in this mode the user is presented with a list of directories to handle. Each row in the table is for a specific WCU and directory, as indicated in the illustration for the UDS mode to the right. To add a row, or directory to fetch, press the button &amp;quot;Add transfer&amp;quot;. An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number and the directory to fetch. You may also choose service area for the transfer, with the default being 0x19. You can add as many entries as you wish.&lt;br /&gt;
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]&lt;br /&gt;
Previously it was possible to manually enter a PIN, that is no longer possible. Instead PINs will be automatically applied if they are available in the portal. For each transfer the specified ECU and area are used to find the correct PIN. For this to be possible PINs must either have been [[Vehicles#Upload Vehicle pins|uploaded from file]] or [[The Portal Administrator View#The Resource Groups Tab|fetched from PIE]].&lt;br /&gt;
&lt;br /&gt;
There is also a button &amp;quot;Check PINs&amp;quot; that will either show which ECUs and areas have PINs available for the vehicle if it is a WCU, or if it is a resource group show which resources have missing PINs.&lt;br /&gt;
&lt;br /&gt;
== ETAS ==&lt;br /&gt;
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
When creating an ETAS task, the task description file you select must be a .exp file.&lt;br /&gt;
&lt;br /&gt;
== Ethernet capture ==&lt;br /&gt;
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 [[Ethernet capture|here]].&lt;br /&gt;
&lt;br /&gt;
== File fetcher ==&lt;br /&gt;
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]&lt;br /&gt;
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.&lt;br /&gt;
&lt;br /&gt;
The following needs to be specified when creating such a task:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;File path&#039;&#039;&#039; - One or several paths to a files or file-containing directories on the unit&#039;s file system. This specifies which files that will be fetched.&lt;br /&gt;
* &#039;&#039;&#039;Username&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;Password&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;IP address&#039;&#039;&#039; - To find the unit.&lt;br /&gt;
* &#039;&#039;&#039;Port&#039;&#039;&#039; -  To find the unit. Default is 22, but can be changed.&lt;br /&gt;
&lt;br /&gt;
Furthermore, the task also allows the use of a proxy.&lt;br /&gt;
&lt;br /&gt;
To use a proxy, the &#039;&#039;&#039;Use Proxy&#039;&#039;&#039; checkbox has to be checked, and the following must be specified:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Proxy Username&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Password&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy IP Address&#039;&#039;&#039; - To find the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Port&#039;&#039;&#039; - To find the proxy unit. Default is 22, but can be changed.&amp;lt;br /&amp;gt;&lt;br /&gt;
== IDC ==&lt;br /&gt;
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 &amp;quot;.seq&amp;quot;). This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== IPEmotion RT ==&lt;br /&gt;
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 &amp;quot;&#039;&#039;.irf&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== LPD ==&lt;br /&gt;
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.&lt;br /&gt;
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]&lt;br /&gt;
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]&lt;br /&gt;
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 &amp;quot;Edit&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
== M-Log ==&lt;br /&gt;
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.[[File:MlogForWiki.png|thumb|M-Log task]]&lt;br /&gt;
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the MLOG - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
==== Software version validation (Available from version 2.74.0) ====&lt;br /&gt;
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|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. &lt;br /&gt;
&lt;br /&gt;
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|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 &amp;quot;Add&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
A negative validation is 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 &amp;quot;Submit&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
If any ECU software versions have changed during the course of running the task it is also possible to edit the task in order to add, edit, or remove ECU SW to be validated anew. &lt;br /&gt;
 &lt;br /&gt;
== MQTT ==&lt;br /&gt;
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.&lt;br /&gt;
&lt;br /&gt;
== Rapid prototyping ==&lt;br /&gt;
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]].&lt;br /&gt;
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]&lt;br /&gt;
The rapid prototyping tab can be seen in Figure &amp;quot;Rapid prototyping task&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
An RP task must consist of at least an &#039;RP binary&#039; or a &#039;Web application zip file&#039;.&lt;br /&gt;
&lt;br /&gt;
== SoftHub ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. &lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;server triggers&#039;&#039;&#039; to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader == &lt;br /&gt;
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]&lt;br /&gt;
Signal Reader is a data capture module that allows monitoring and logging of CAN, LIN 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:&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Chosen file&amp;quot; field.&lt;br /&gt;
&lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting &amp;quot;Monitor signals&amp;quot;. 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 &#039;&#039;&#039;Monitor Signals&#039;&#039;&#039; 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&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;Server Triggers&#039;&#039;&#039; to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
=== The Signal Broker === &lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
=== Files containing references to sequence files === &lt;br /&gt;
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] &lt;br /&gt;
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 &#039;&#039;Snapshots&#039;&#039; or &#039;&#039;Extended data&#039;&#039;. An example of this can found in Figure &amp;quot;Sequence Files References in .haf File&amp;quot;. &lt;br /&gt;
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] &lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Sequence File with Functional Query&amp;quot; we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read &#039;&#039;Extended data&#039;&#039;. It is also possible to select both &#039;&#039;Snapshots&#039;&#039; and &#039;&#039;Extended data&#039;&#039;.  &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== WICE internal signals ===&lt;br /&gt;
In addition to CAN and other 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]]&lt;br /&gt;
&lt;br /&gt;
=== User Defined signals ===&lt;br /&gt;
You can define new signals by combining signals using [[Logical expressions]], [[Arithmetic expressions]] and Special expressions. The user defined signals can be recorded and can be used in Trigger expressions.&lt;br /&gt;
&lt;br /&gt;
== SoH ==&lt;br /&gt;
[[File:SoH.png|thumb|799x799px|SoH]]&lt;br /&gt;
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 &amp;quot;SoH&amp;quot;. 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_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:&lt;br /&gt;
*Mileage&lt;br /&gt;
*Voltage&lt;br /&gt;
*Read ECU software numbers&lt;br /&gt;
*Read ECU DTC:s (optionally including &#039;Snapshot&#039; and &#039;Extended data&#039;)&lt;br /&gt;
*Read OBD-II PIDs&lt;br /&gt;
*App Diagnotstic Db Part Num&lt;br /&gt;
*Build ID&lt;br /&gt;
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]&lt;br /&gt;
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)&lt;br /&gt;
*Clear DTCs. &lt;br /&gt;
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)&lt;br /&gt;
**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)&lt;br /&gt;
*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 task. It is a text type of file. In addition, a system value label called &#039;engine_hours&#039; (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle.  &lt;br /&gt;
&lt;br /&gt;
This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
Some selections above might not be available to you as this is a configuration setting depending on customer.&lt;br /&gt;
&lt;br /&gt;
== SWDL ==&lt;br /&gt;
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]&lt;br /&gt;
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. &amp;lt;code&amp;gt;ff:00:1a:2c:77&amp;lt;/code&amp;gt; (or alternatively, omitting the colon separator, &amp;lt;code&amp;gt;ff001a2c77&amp;lt;/code&amp;gt;). 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 &amp;quot;New SWDL task&amp;quot;. To get an overview of how the files relate to the ECUs it is possible to choose the &amp;quot;Group by&amp;quot;-option when right clicking the ECU column in the file table. &lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;pre-update sequence file and/or a post-update sequence file&#039;&#039;&#039;. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include one &#039;&#039;&#039;signature file&#039;&#039;&#039; (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)&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;VGM unlock&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
By checking the box &#039;&#039;&#039;Run SoH after completion&#039;&#039;&#039; it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.&lt;br /&gt;
&lt;br /&gt;
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box &amp;quot;&#039;&#039;&#039;Use Vehicle Pin mappings&#039;&#039;&#039;&amp;quot;. 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 [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally contain a &#039;&#039;&#039;Trigger Expression&#039;&#039;&#039; which must be fulfilled within a specified time limit (&amp;quot;Wait time&amp;quot;) 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.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
It is also possible to choose to &#039;&#039;&#039;ignore checksums&#039;&#039;&#039; and/or &#039;&#039;&#039;disable pre-programming&#039;&#039;&#039; using the corresponding checkboxes.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
== Video ==&lt;br /&gt;
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:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: To initiate the recording you need to attach a button to the WCU in order to start in the video recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader &#039;&#039;recorder&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)&lt;br /&gt;
&lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time (not valid in the cases of the &#039;None&#039; trigger option above). As an example, let&#039;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.&lt;br /&gt;
&lt;br /&gt;
A maximum &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Read more about the video support in WICE [[WICE_video|here]].&lt;br /&gt;
&lt;br /&gt;
== Applicable for all types ==&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]].&lt;br /&gt;
&lt;br /&gt;
=== Site specific features ===&lt;br /&gt;
&lt;br /&gt;
==== Announce result file availability ====&lt;br /&gt;
[[File:Resultfilepanel.png|thumb|Announced On column]]&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there&#039;s a new &#039;Announced On&#039; column that keeps track of when the result file was announced.&lt;br /&gt;
&lt;br /&gt;
==== Retention time ====&lt;br /&gt;
[[File:Retention time.png|thumb|435x435px|Retention time]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
It is possible to set a default retention time for resource groups. To do this, add a global value label named &#039;&#039;&#039;RETENTION_TIME&#039;&#039;&#039; 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.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4260</id>
		<title>Creating a Task</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4260"/>
		<updated>2026-09-22T11:28:29Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* WICE internal signals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;includeonly&amp;gt;== Creating a Task==&amp;lt;/includeonly&amp;gt;&lt;br /&gt;
You create a new task by pressing the &amp;quot;New Task&amp;quot; button on the bottom of the &amp;quot;Tasks&amp;quot; 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 &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_in_progress&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt; or &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_done&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;. 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. &lt;br /&gt;
&lt;br /&gt;
To learn about how to add resources to the task, check [[New task|here]].&lt;br /&gt;
&lt;br /&gt;
== Arcos ==&lt;br /&gt;
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]&lt;br /&gt;
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 &amp;quot;&#039;&#039;.ccmc&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the Arcos - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== Area5 ==&lt;br /&gt;
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]&lt;br /&gt;
Area5 tasks are used to read out data from the memory of ECUs. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Assignment:&#039;&#039;&#039; To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Validate ECU SW version on WCU:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Trigger Expression:&#039;&#039;&#039; 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]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Sync Signal:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
== Audio ==&lt;br /&gt;
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader &#039;&#039;&#039;recorder&#039;&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;Audio level&#039;&#039;&#039;: Start the trigger once the microphone registers volume above a certain threshold.&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible.&lt;br /&gt;
  &lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let&#039;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 &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
It is possible to monitor the audio live. To do this, check the box &amp;quot;Monitoring&amp;quot;. To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. &lt;br /&gt;
&lt;br /&gt;
There is more information about audio in WICE [[Wice audio|here]].&lt;br /&gt;
&lt;br /&gt;
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== Blue piraT ==&lt;br /&gt;
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 &amp;quot;extra bundle&amp;quot;). Contact Alkit Communications in order to set this up.&lt;br /&gt;
&lt;br /&gt;
== CAN-recorder ==&lt;br /&gt;
[[File:Canrecorder.png|thumb|Canrecorder]]&lt;br /&gt;
Canrecorder is a measurement module that allows CAN frames to be captured and logged.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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”&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Scheduling=== &lt;br /&gt;
&lt;br /&gt;
For WCUs with version &amp;gt;= 2.53 this task can be scheduled by selecting the &amp;quot;Add schedule&amp;quot;-checkbox. By doing so, the panel shown in Figure &amp;quot;Schedule Panel&amp;quot; appears. By thereafter selecting the &amp;quot;ASAP&amp;quot; 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 &amp;quot;Time span&amp;quot; and &amp;quot;Repeat&amp;quot;-checkboxes and select the sought time in the &amp;quot;Start field&amp;quot;. The task can also be performed within a certain time span, and in this case &amp;quot;Time span&amp;quot; should be checked and the Date in &amp;quot;End&amp;quot; field specified. Repetition of the task is defined by checking the &amp;quot;Repeat&amp;quot; checkbox, defining a interval size in the field after &amp;quot;Every&amp;quot; and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the &amp;quot;Until&amp;quot; field is reached. By selecting the &amp;quot;On ignition&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]&lt;br /&gt;
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with &#039;On ignition&#039; enabled]]&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To control the time zone in which the task scheduling is to be performed the &amp;quot;WCU local time&amp;quot;-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 &amp;gt;= 2.53 by an administrator using &amp;quot;Edit configuration&amp;quot; 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 &amp;quot;WCU local time&amp;quot;-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.&lt;br /&gt;
&lt;br /&gt;
== Diagnostic Log and Trace (DLT) ==&lt;br /&gt;
The DLT functionality comes in two flavors. One is based on communicating with a DLT daemon on the ECU and the other is based on the UDS service 38. You switch between the using the button &amp;quot;DLT UDS mode&amp;quot;. &lt;br /&gt;
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]&lt;br /&gt;
From version 2.96 it also possible to create a task with DLT daemon and DLT UDS mode enabled at the same time by checking the &amp;quot;Enable multi task&amp;quot; checkbox as can be seen in the screenshot the right. &lt;br /&gt;
&lt;br /&gt;
=== DLT Daemon Mode ===&lt;br /&gt;
DLT itself provides a log and trace interface, based on the standardized 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 [https://github.com/GENIVI/dlt-daemon here]. &lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:&lt;br /&gt;
&lt;br /&gt;
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check &amp;quot;Use vehicle announcement&amp;quot; (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.&lt;br /&gt;
# Daemon port - which port on the address the daemon is at.&lt;br /&gt;
# 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 [https://github.com/GENIVI/dlt-daemon#learn-more here].&lt;br /&gt;
&lt;br /&gt;
=== DLT UDS Mode ===&lt;br /&gt;
When in this mode the user is presented with a list of directories to handle. Each row in the table is for a specific WCU and directory, as indicated in the illustration for the UDS mode to the right. To add a row, or directory to fetch, press the button &amp;quot;Add transfer&amp;quot;. An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number and the directory to fetch. You may also choose service area for the transfer, with the default being 0x19. You can add as many entries as you wish.&lt;br /&gt;
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]&lt;br /&gt;
Previously it was possible to manually enter a PIN, that is no longer possible. Instead PINs will be automatically applied if they are available in the portal. For each transfer the specified ECU and area are used to find the correct PIN. For this to be possible PINs must either have been [[Vehicles#Upload Vehicle pins|uploaded from file]] or [[The Portal Administrator View#The Resource Groups Tab|fetched from PIE]].&lt;br /&gt;
&lt;br /&gt;
There is also a button &amp;quot;Check PINs&amp;quot; that will either show which ECUs and areas have PINs available for the vehicle if it is a WCU, or if it is a resource group show which resources have missing PINs.&lt;br /&gt;
&lt;br /&gt;
== ETAS ==&lt;br /&gt;
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
When creating an ETAS task, the task description file you select must be a .exp file.&lt;br /&gt;
&lt;br /&gt;
== Ethernet capture ==&lt;br /&gt;
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 [[Ethernet capture|here]].&lt;br /&gt;
&lt;br /&gt;
== File fetcher ==&lt;br /&gt;
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]&lt;br /&gt;
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.&lt;br /&gt;
&lt;br /&gt;
The following needs to be specified when creating such a task:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;File path&#039;&#039;&#039; - One or several paths to a files or file-containing directories on the unit&#039;s file system. This specifies which files that will be fetched.&lt;br /&gt;
* &#039;&#039;&#039;Username&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;Password&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;IP address&#039;&#039;&#039; - To find the unit.&lt;br /&gt;
* &#039;&#039;&#039;Port&#039;&#039;&#039; -  To find the unit. Default is 22, but can be changed.&lt;br /&gt;
&lt;br /&gt;
Furthermore, the task also allows the use of a proxy.&lt;br /&gt;
&lt;br /&gt;
To use a proxy, the &#039;&#039;&#039;Use Proxy&#039;&#039;&#039; checkbox has to be checked, and the following must be specified:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Proxy Username&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Password&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy IP Address&#039;&#039;&#039; - To find the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Port&#039;&#039;&#039; - To find the proxy unit. Default is 22, but can be changed.&amp;lt;br /&amp;gt;&lt;br /&gt;
== IDC ==&lt;br /&gt;
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 &amp;quot;.seq&amp;quot;). This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== IPEmotion RT ==&lt;br /&gt;
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 &amp;quot;&#039;&#039;.irf&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== LPD ==&lt;br /&gt;
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.&lt;br /&gt;
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]&lt;br /&gt;
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]&lt;br /&gt;
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 &amp;quot;Edit&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
== M-Log ==&lt;br /&gt;
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.[[File:MlogForWiki.png|thumb|M-Log task]]&lt;br /&gt;
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the MLOG - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
==== Software version validation (Available from version 2.74.0) ====&lt;br /&gt;
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|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. &lt;br /&gt;
&lt;br /&gt;
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|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 &amp;quot;Add&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
A negative validation is 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 &amp;quot;Submit&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
If any ECU software versions have changed during the course of running the task it is also possible to edit the task in order to add, edit, or remove ECU SW to be validated anew. &lt;br /&gt;
 &lt;br /&gt;
== MQTT ==&lt;br /&gt;
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.&lt;br /&gt;
&lt;br /&gt;
== Rapid prototyping ==&lt;br /&gt;
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]].&lt;br /&gt;
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]&lt;br /&gt;
The rapid prototyping tab can be seen in Figure &amp;quot;Rapid prototyping task&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
An RP task must consist of at least an &#039;RP binary&#039; or a &#039;Web application zip file&#039;.&lt;br /&gt;
&lt;br /&gt;
== SoftHub ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. &lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;server triggers&#039;&#039;&#039; to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader == &lt;br /&gt;
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]&lt;br /&gt;
Signal Reader is a data capture module that allows monitoring and logging of CAN, LIN 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:&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Chosen file&amp;quot; field.&lt;br /&gt;
&lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting &amp;quot;Monitor signals&amp;quot;. 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 &#039;&#039;&#039;Monitor Signals&#039;&#039;&#039; 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&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;Server Triggers&#039;&#039;&#039; to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
=== The Signal Broker === &lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
=== Files containing references to sequence files === &lt;br /&gt;
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] &lt;br /&gt;
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 &#039;&#039;Snapshots&#039;&#039; or &#039;&#039;Extended data&#039;&#039;. An example of this can found in Figure &amp;quot;Sequence Files References in .haf File&amp;quot;. &lt;br /&gt;
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] &lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Sequence File with Functional Query&amp;quot; we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read &#039;&#039;Extended data&#039;&#039;. It is also possible to select both &#039;&#039;Snapshots&#039;&#039; and &#039;&#039;Extended data&#039;&#039;.  &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== WICE internal signals ===&lt;br /&gt;
In addition to CAN and other 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]]&lt;br /&gt;
&lt;br /&gt;
== SoH ==&lt;br /&gt;
[[File:SoH.png|thumb|799x799px|SoH]]&lt;br /&gt;
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 &amp;quot;SoH&amp;quot;. 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_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:&lt;br /&gt;
*Mileage&lt;br /&gt;
*Voltage&lt;br /&gt;
*Read ECU software numbers&lt;br /&gt;
*Read ECU DTC:s (optionally including &#039;Snapshot&#039; and &#039;Extended data&#039;)&lt;br /&gt;
*Read OBD-II PIDs&lt;br /&gt;
*App Diagnotstic Db Part Num&lt;br /&gt;
*Build ID&lt;br /&gt;
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]&lt;br /&gt;
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)&lt;br /&gt;
*Clear DTCs. &lt;br /&gt;
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)&lt;br /&gt;
**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)&lt;br /&gt;
*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 task. It is a text type of file. In addition, a system value label called &#039;engine_hours&#039; (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle.  &lt;br /&gt;
&lt;br /&gt;
This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
Some selections above might not be available to you as this is a configuration setting depending on customer.&lt;br /&gt;
&lt;br /&gt;
== SWDL ==&lt;br /&gt;
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]&lt;br /&gt;
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. &amp;lt;code&amp;gt;ff:00:1a:2c:77&amp;lt;/code&amp;gt; (or alternatively, omitting the colon separator, &amp;lt;code&amp;gt;ff001a2c77&amp;lt;/code&amp;gt;). 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 &amp;quot;New SWDL task&amp;quot;. To get an overview of how the files relate to the ECUs it is possible to choose the &amp;quot;Group by&amp;quot;-option when right clicking the ECU column in the file table. &lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;pre-update sequence file and/or a post-update sequence file&#039;&#039;&#039;. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include one &#039;&#039;&#039;signature file&#039;&#039;&#039; (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)&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;VGM unlock&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
By checking the box &#039;&#039;&#039;Run SoH after completion&#039;&#039;&#039; it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.&lt;br /&gt;
&lt;br /&gt;
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box &amp;quot;&#039;&#039;&#039;Use Vehicle Pin mappings&#039;&#039;&#039;&amp;quot;. 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 [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally contain a &#039;&#039;&#039;Trigger Expression&#039;&#039;&#039; which must be fulfilled within a specified time limit (&amp;quot;Wait time&amp;quot;) 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.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
It is also possible to choose to &#039;&#039;&#039;ignore checksums&#039;&#039;&#039; and/or &#039;&#039;&#039;disable pre-programming&#039;&#039;&#039; using the corresponding checkboxes.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
== Video ==&lt;br /&gt;
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:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: To initiate the recording you need to attach a button to the WCU in order to start in the video recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader &#039;&#039;recorder&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)&lt;br /&gt;
&lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time (not valid in the cases of the &#039;None&#039; trigger option above). As an example, let&#039;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.&lt;br /&gt;
&lt;br /&gt;
A maximum &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Read more about the video support in WICE [[WICE_video|here]].&lt;br /&gt;
&lt;br /&gt;
== Applicable for all types ==&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]].&lt;br /&gt;
&lt;br /&gt;
=== Site specific features ===&lt;br /&gt;
&lt;br /&gt;
==== Announce result file availability ====&lt;br /&gt;
[[File:Resultfilepanel.png|thumb|Announced On column]]&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there&#039;s a new &#039;Announced On&#039; column that keeps track of when the result file was announced.&lt;br /&gt;
&lt;br /&gt;
==== Retention time ====&lt;br /&gt;
[[File:Retention time.png|thumb|435x435px|Retention time]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
It is possible to set a default retention time for resource groups. To do this, add a global value label named &#039;&#039;&#039;RETENTION_TIME&#039;&#039;&#039; 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.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4259</id>
		<title>Creating a Task</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Creating_a_Task&amp;diff=4259"/>
		<updated>2026-09-22T11:27:06Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Signal Reader */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;includeonly&amp;gt;== Creating a Task==&amp;lt;/includeonly&amp;gt;&lt;br /&gt;
You create a new task by pressing the &amp;quot;New Task&amp;quot; button on the bottom of the &amp;quot;Tasks&amp;quot; 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 &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_in_progress&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt; or &amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;shelving_done&amp;lt;nowiki&amp;gt;&#039;&#039;&amp;lt;/nowiki&amp;gt;. 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. &lt;br /&gt;
&lt;br /&gt;
To learn about how to add resources to the task, check [[New task|here]].&lt;br /&gt;
&lt;br /&gt;
== Arcos ==&lt;br /&gt;
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]&lt;br /&gt;
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 &amp;quot;&#039;&#039;.ccmc&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the Arcos - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== Area5 ==&lt;br /&gt;
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]&lt;br /&gt;
Area5 tasks are used to read out data from the memory of ECUs. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Assignment:&#039;&#039;&#039; To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Validate ECU SW version on WCU:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Trigger Expression:&#039;&#039;&#039; 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]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Sync Signal:&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
== Audio ==&lt;br /&gt;
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader &#039;&#039;&#039;recorder&#039;&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;Audio level&#039;&#039;&#039;: Start the trigger once the microphone registers volume above a certain threshold.&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible.&lt;br /&gt;
  &lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let&#039;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 &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
It is possible to monitor the audio live. To do this, check the box &amp;quot;Monitoring&amp;quot;. To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. &lt;br /&gt;
&lt;br /&gt;
There is more information about audio in WICE [[Wice audio|here]].&lt;br /&gt;
&lt;br /&gt;
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== Blue piraT ==&lt;br /&gt;
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 &amp;quot;extra bundle&amp;quot;). Contact Alkit Communications in order to set this up.&lt;br /&gt;
&lt;br /&gt;
== CAN-recorder ==&lt;br /&gt;
[[File:Canrecorder.png|thumb|Canrecorder]]&lt;br /&gt;
Canrecorder is a measurement module that allows CAN frames to be captured and logged.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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”&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
===Scheduling=== &lt;br /&gt;
&lt;br /&gt;
For WCUs with version &amp;gt;= 2.53 this task can be scheduled by selecting the &amp;quot;Add schedule&amp;quot;-checkbox. By doing so, the panel shown in Figure &amp;quot;Schedule Panel&amp;quot; appears. By thereafter selecting the &amp;quot;ASAP&amp;quot; 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 &amp;quot;Time span&amp;quot; and &amp;quot;Repeat&amp;quot;-checkboxes and select the sought time in the &amp;quot;Start field&amp;quot;. The task can also be performed within a certain time span, and in this case &amp;quot;Time span&amp;quot; should be checked and the Date in &amp;quot;End&amp;quot; field specified. Repetition of the task is defined by checking the &amp;quot;Repeat&amp;quot; checkbox, defining a interval size in the field after &amp;quot;Every&amp;quot; and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the &amp;quot;Until&amp;quot; field is reached. By selecting the &amp;quot;On ignition&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]&lt;br /&gt;
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with &#039;On ignition&#039; enabled]]&lt;br /&gt;
&amp;lt;br clear=&amp;quot;all&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To control the time zone in which the task scheduling is to be performed the &amp;quot;WCU local time&amp;quot;-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 &amp;gt;= 2.53 by an administrator using &amp;quot;Edit configuration&amp;quot; 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 &amp;quot;WCU local time&amp;quot;-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.&lt;br /&gt;
&lt;br /&gt;
== Diagnostic Log and Trace (DLT) ==&lt;br /&gt;
The DLT functionality comes in two flavors. One is based on communicating with a DLT daemon on the ECU and the other is based on the UDS service 38. You switch between the using the button &amp;quot;DLT UDS mode&amp;quot;. &lt;br /&gt;
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]&lt;br /&gt;
From version 2.96 it also possible to create a task with DLT daemon and DLT UDS mode enabled at the same time by checking the &amp;quot;Enable multi task&amp;quot; checkbox as can be seen in the screenshot the right. &lt;br /&gt;
&lt;br /&gt;
=== DLT Daemon Mode ===&lt;br /&gt;
DLT itself provides a log and trace interface, based on the standardized 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 [https://github.com/GENIVI/dlt-daemon here]. &lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:&lt;br /&gt;
&lt;br /&gt;
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check &amp;quot;Use vehicle announcement&amp;quot; (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.&lt;br /&gt;
# Daemon port - which port on the address the daemon is at.&lt;br /&gt;
# 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 [https://github.com/GENIVI/dlt-daemon#learn-more here].&lt;br /&gt;
&lt;br /&gt;
=== DLT UDS Mode ===&lt;br /&gt;
When in this mode the user is presented with a list of directories to handle. Each row in the table is for a specific WCU and directory, as indicated in the illustration for the UDS mode to the right. To add a row, or directory to fetch, press the button &amp;quot;Add transfer&amp;quot;. An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number and the directory to fetch. You may also choose service area for the transfer, with the default being 0x19. You can add as many entries as you wish.&lt;br /&gt;
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]&lt;br /&gt;
Previously it was possible to manually enter a PIN, that is no longer possible. Instead PINs will be automatically applied if they are available in the portal. For each transfer the specified ECU and area are used to find the correct PIN. For this to be possible PINs must either have been [[Vehicles#Upload Vehicle pins|uploaded from file]] or [[The Portal Administrator View#The Resource Groups Tab|fetched from PIE]].&lt;br /&gt;
&lt;br /&gt;
There is also a button &amp;quot;Check PINs&amp;quot; that will either show which ECUs and areas have PINs available for the vehicle if it is a WCU, or if it is a resource group show which resources have missing PINs.&lt;br /&gt;
&lt;br /&gt;
== ETAS ==&lt;br /&gt;
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
When creating an ETAS task, the task description file you select must be a .exp file.&lt;br /&gt;
&lt;br /&gt;
== Ethernet capture ==&lt;br /&gt;
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 [[Ethernet capture|here]].&lt;br /&gt;
&lt;br /&gt;
== File fetcher ==&lt;br /&gt;
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]&lt;br /&gt;
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.&lt;br /&gt;
&lt;br /&gt;
The following needs to be specified when creating such a task:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;File path&#039;&#039;&#039; - One or several paths to a files or file-containing directories on the unit&#039;s file system. This specifies which files that will be fetched.&lt;br /&gt;
* &#039;&#039;&#039;Username&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;Password&#039;&#039;&#039; - To log in to the unit.&lt;br /&gt;
* &#039;&#039;&#039;IP address&#039;&#039;&#039; - To find the unit.&lt;br /&gt;
* &#039;&#039;&#039;Port&#039;&#039;&#039; -  To find the unit. Default is 22, but can be changed.&lt;br /&gt;
&lt;br /&gt;
Furthermore, the task also allows the use of a proxy.&lt;br /&gt;
&lt;br /&gt;
To use a proxy, the &#039;&#039;&#039;Use Proxy&#039;&#039;&#039; checkbox has to be checked, and the following must be specified:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Proxy Username&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Password&#039;&#039;&#039; - To log in to the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy IP Address&#039;&#039;&#039; - To find the proxy unit.&lt;br /&gt;
* &#039;&#039;&#039;Proxy Port&#039;&#039;&#039; - To find the proxy unit. Default is 22, but can be changed.&amp;lt;br /&amp;gt;&lt;br /&gt;
== IDC ==&lt;br /&gt;
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 &amp;quot;.seq&amp;quot;). This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
== IPEmotion RT ==&lt;br /&gt;
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 &amp;quot;&#039;&#039;.irf&#039;&#039;&amp;quot;. 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.&lt;br /&gt;
&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
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 [[Creating a Task#Software version validation (Available from version 2.74.0)|Software version validation]]).&lt;br /&gt;
&lt;br /&gt;
== LPD ==&lt;br /&gt;
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.&lt;br /&gt;
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]&lt;br /&gt;
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]&lt;br /&gt;
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 &amp;quot;Edit&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
== M-Log ==&lt;br /&gt;
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.[[File:MlogForWiki.png|thumb|M-Log task]]&lt;br /&gt;
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]&lt;br /&gt;
Select the &amp;quot;Use existing measurement configuration&amp;quot; checkbox if a measurement setup file already exists on the MLOG - no upload will be required.&lt;br /&gt;
&lt;br /&gt;
==== Software version validation (Available from version 2.74.0) ====&lt;br /&gt;
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|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. &lt;br /&gt;
&lt;br /&gt;
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|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 &amp;quot;Add&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
A negative validation is 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 &amp;quot;Submit&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
If any ECU software versions have changed during the course of running the task it is also possible to edit the task in order to add, edit, or remove ECU SW to be validated anew. &lt;br /&gt;
 &lt;br /&gt;
== MQTT ==&lt;br /&gt;
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.&lt;br /&gt;
&lt;br /&gt;
== Rapid prototyping ==&lt;br /&gt;
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]].&lt;br /&gt;
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]&lt;br /&gt;
The rapid prototyping tab can be seen in Figure &amp;quot;Rapid prototyping task&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
An RP task must consist of at least an &#039;RP binary&#039; or a &#039;Web application zip file&#039;.&lt;br /&gt;
&lt;br /&gt;
== SoftHub ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. &lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;server triggers&#039;&#039;&#039; to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader == &lt;br /&gt;
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]&lt;br /&gt;
Signal Reader is a data capture module that allows monitoring and logging of CAN, LIN 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:&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Chosen file&amp;quot; field.&lt;br /&gt;
&lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting &amp;quot;Monitor signals&amp;quot;. 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 &#039;&#039;&#039;Monitor Signals&#039;&#039;&#039; 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&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
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 &#039;&#039;&#039;Server Triggers&#039;&#039;&#039; to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].&lt;br /&gt;
&lt;br /&gt;
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
=== The Signal Broker === &lt;br /&gt;
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]].&lt;br /&gt;
&lt;br /&gt;
=== Files containing references to sequence files === &lt;br /&gt;
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] &lt;br /&gt;
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 &#039;&#039;Snapshots&#039;&#039; or &#039;&#039;Extended data&#039;&#039;. An example of this can found in Figure &amp;quot;Sequence Files References in .haf File&amp;quot;. &lt;br /&gt;
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] &lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;Sequence File with Functional Query&amp;quot; we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read &#039;&#039;Extended data&#039;&#039;. It is also possible to select both &#039;&#039;Snapshots&#039;&#039; and &#039;&#039;Extended data&#039;&#039;.  &lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== WICE internal signals ===&lt;br /&gt;
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]]&lt;br /&gt;
&lt;br /&gt;
== SoH ==&lt;br /&gt;
[[File:SoH.png|thumb|799x799px|SoH]]&lt;br /&gt;
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 &amp;quot;SoH&amp;quot;. 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_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:&lt;br /&gt;
*Mileage&lt;br /&gt;
*Voltage&lt;br /&gt;
*Read ECU software numbers&lt;br /&gt;
*Read ECU DTC:s (optionally including &#039;Snapshot&#039; and &#039;Extended data&#039;)&lt;br /&gt;
*Read OBD-II PIDs&lt;br /&gt;
*App Diagnotstic Db Part Num&lt;br /&gt;
*Build ID&lt;br /&gt;
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]&lt;br /&gt;
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)&lt;br /&gt;
*Clear DTCs. &lt;br /&gt;
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)&lt;br /&gt;
**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)&lt;br /&gt;
*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 task. It is a text type of file. In addition, a system value label called &#039;engine_hours&#039; (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle.  &lt;br /&gt;
&lt;br /&gt;
This task can also be scheduled in the same manner as described for the Canrecoder task.&lt;br /&gt;
&lt;br /&gt;
Some selections above might not be available to you as this is a configuration setting depending on customer.&lt;br /&gt;
&lt;br /&gt;
== SWDL ==&lt;br /&gt;
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]&lt;br /&gt;
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. &amp;lt;code&amp;gt;ff:00:1a:2c:77&amp;lt;/code&amp;gt; (or alternatively, omitting the colon separator, &amp;lt;code&amp;gt;ff001a2c77&amp;lt;/code&amp;gt;). 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 &amp;quot;New SWDL task&amp;quot;. To get an overview of how the files relate to the ECUs it is possible to choose the &amp;quot;Group by&amp;quot;-option when right clicking the ECU column in the file table. &lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;pre-update sequence file and/or a post-update sequence file&#039;&#039;&#039;. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include one &#039;&#039;&#039;signature file&#039;&#039;&#039; (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)&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally include a &#039;&#039;&#039;VGM unlock&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
By checking the box &#039;&#039;&#039;Run SoH after completion&#039;&#039;&#039; it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.&lt;br /&gt;
&lt;br /&gt;
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box &amp;quot;&#039;&#039;&#039;Use Vehicle Pin mappings&#039;&#039;&#039;&amp;quot;. 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 [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].&lt;br /&gt;
&lt;br /&gt;
SWDL tasks can optionally contain a &#039;&#039;&#039;Trigger Expression&#039;&#039;&#039; which must be fulfilled within a specified time limit (&amp;quot;Wait time&amp;quot;) 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.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
It is also possible to choose to &#039;&#039;&#039;ignore checksums&#039;&#039;&#039; and/or &#039;&#039;&#039;disable pre-programming&#039;&#039;&#039; using the corresponding checkboxes.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
== Video ==&lt;br /&gt;
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:&lt;br /&gt;
* &#039;&#039;&#039;Trigger button&#039;&#039;&#039;: To initiate the recording you need to attach a button to the WCU in order to start in the video recording.&lt;br /&gt;
* &#039;&#039;&#039;Signal reader&#039;&#039;&#039;: Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader &#039;&#039;recorder&#039;&#039; 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 &amp;quot;auto&amp;quot; as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. &lt;br /&gt;
* &#039;&#039;&#039;Expression&#039;&#039;&#039;: Similar to the &#039;Signal reader&#039; trigger option, the &#039;Expression&#039; 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 &#039;Signal Reader&#039; 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]].&lt;br /&gt;
* &#039;&#039;&#039;None&#039;&#039;&#039;: start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)&lt;br /&gt;
&lt;br /&gt;
In addition to this, you can set the &#039;&#039;&#039;pre-trig&#039;&#039;&#039; time (not valid in the cases of the &#039;None&#039; trigger option above). As an example, let&#039;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.&lt;br /&gt;
&lt;br /&gt;
A maximum &#039;&#039;&#039;duration&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Read more about the video support in WICE [[WICE_video|here]].&lt;br /&gt;
&lt;br /&gt;
== Applicable for all types ==&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]].&lt;br /&gt;
&lt;br /&gt;
=== Site specific features ===&lt;br /&gt;
&lt;br /&gt;
==== Announce result file availability ====&lt;br /&gt;
[[File:Resultfilepanel.png|thumb|Announced On column]]&lt;br /&gt;
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 &amp;quot;Announce result file availability&amp;quot;, this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there&#039;s a new &#039;Announced On&#039; column that keeps track of when the result file was announced.&lt;br /&gt;
&lt;br /&gt;
==== Retention time ====&lt;br /&gt;
[[File:Retention time.png|thumb|435x435px|Retention time]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
It is possible to set a default retention time for resource groups. To do this, add a global value label named &#039;&#039;&#039;RETENTION_TIME&#039;&#039;&#039; 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.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Assignment_Editor&amp;diff=4244</id>
		<title>Signal Reader Assignment Editor</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Assignment_Editor&amp;diff=4244"/>
		<updated>2026-09-09T11:16:26Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Signal Reader Assignment Editor can be found under the tab &#039;&#039;&#039;Assignment&#039;&#039;&#039; and allows the user to create new assignments for Signal Reader directly in the portal. This page will guide you through the basics of using the editor.&lt;br /&gt;
&lt;br /&gt;
==Edit/Create a signal reader assignment==&lt;br /&gt;
&lt;br /&gt;
The first tab that you are presented with is the &#039;&#039;&#039;Assignment global settings&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Under the &#039;&#039;&#039;Measurements&#039;&#039;&#039; tab, see Figure &amp;quot;Measurement Setups&amp;quot;, 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 &#039;&#039;&#039;Triggers&#039;&#039;&#039; that activate and deactivate on certain conditions provided by the user. Each trigger can contain a &#039;&#039;&#039;Recorder&#039;&#039;&#039; 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 &#039;&#039;&#039;setup switch&#039;&#039;&#039;.[[File:Measurement setup.png|none|thumb|608x608px|Measurement Setups]]&lt;br /&gt;
When you feel finished with the assignment you can simply click the &#039;&#039;&#039;Save assignment&#039;&#039;&#039; button in the lower right corner to save the assignment in its current state.&lt;br /&gt;
===Trigger===&lt;br /&gt;
To add a trigger to a measurement setup, click the &#039;&#039;&#039;plus&#039;&#039;&#039; 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. In the window, trigger type can be set to different types: &#039;&#039;&#039;Recorder&#039;&#039;&#039;, &#039;&#039;&#039;Setup switch&#039;&#039;&#039;, &#039;&#039;&#039;Pause diagnostics&#039;&#039;&#039;, &#039;&#039;&#039;Start/stop CCP DAQ&#039;&#039;&#039;, &#039;&#039;&#039;Start/stop XCP DAQ&#039;&#039;&#039;, &#039;&#039;&#039;Upload&#039;&#039;&#039; and &#039;&#039;&#039;Vehicle ethernet&#039;&#039;&#039;. With Setup switch you will jump/end/restart when the start condition is met.&lt;br /&gt;
&lt;br /&gt;
Fill out the &#039;&#039;&#039;start trigger&#039;&#039;&#039; &#039;&#039;&#039;condition&#039;&#039;&#039; for the trigger. This is easiest to do in the &#039;&#039;&#039;Edit expression&#039;&#039;&#039; window that you can get to by clicking one of the &#039;&#039;&#039;Edit&#039;&#039;&#039; buttons. To find a new signal to add a condition for, use the &#039;&#039;&#039;Add signal&#039;&#039;&#039; button. Here, you can browse all signals available for this assignment. Use the dropdown to browse signals from different can-busses and Wice internal signals. If you want to browse the signals currently in use in the assignment for the selected signal source, check the &#039;&#039;&#039;Search in assignment&#039;&#039;&#039; box. If you want more information about a signal, select it and click &#039;&#039;&#039;More info&#039;&#039;&#039;. When you have found the signal you want, double click it or select it and click &#039;&#039;&#039;Add signal&#039;&#039;&#039;. Now you can use the &#039;&#039;&#039;Operators&#039;&#039;&#039; list to add a condition for the signal, for example &amp;quot; &amp;gt; 0&amp;quot;. 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 &amp;quot;Validate Button States&amp;quot; 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|link=https://wiki.alkit.se/wice264/index.php/File:ValidateButtonStates.png|none]]A &#039;&#039;&#039;stop trigger condition&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
==== Speciel purpose trigger ====&lt;br /&gt;
&lt;br /&gt;
* Recorder&lt;br /&gt;
** Start Trigger - Start recording&lt;br /&gt;
** Stop Trigger - Stop recording&lt;br /&gt;
* Setup switch&lt;br /&gt;
** Start Trigger - Jumps to selected measurement setup&lt;br /&gt;
** Stop Trigger - N/A&lt;br /&gt;
* Pause diagnostics&lt;br /&gt;
** Start Trigger - Pauses sending of diagnostic requests&lt;br /&gt;
** Stop Trigger - Resumes sending of disgnostic requests&lt;br /&gt;
* Start/Stop CCP DAQ&lt;br /&gt;
** Start Trigger - Starts transmission of CCP DAQ lists&lt;br /&gt;
** Stop Trigger - Stops transmission of CCP DAQ lists&lt;br /&gt;
* Start/stop XCP DAQ&lt;br /&gt;
** Start Trigger - Starts transmission of XCP DAQ lists&lt;br /&gt;
** Stop Trigger - Stops transmission of XCP DAQ lists&lt;br /&gt;
* Upload&lt;br /&gt;
** Start Trigger - Will trigger to upload collected data to Portal&lt;br /&gt;
** Stop Trigger - N/A&lt;br /&gt;
* Vehicle ethernet&lt;br /&gt;
** Start Trigger - Activate vehicle ethernet&lt;br /&gt;
** Stop Trigger - Deactivate vehicle ethernet&lt;br /&gt;
&lt;br /&gt;
===Recorder===&lt;br /&gt;
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.&lt;br /&gt;
====Recorder - DREC====&lt;br /&gt;
DREC (Diagnostics recorder) is used to send diagnostic requests onto the vehicle&#039;s communication buses and record the responses. The diagnostic requests are supplied in a sequence file uploaded by the user. The sequence file contains one diagnostic request per line, with the ECU id at the beginning of the line. There can optionally be other information as well. The syntax is the same as the one used for the IDC module, see [[IDC Sequence File Syntax|Sequence File Syntax]]. The result from a DREC will be a diagnostic log file, a text file containing both the requests from the sequence file and the corresponding responses.&lt;br /&gt;
&lt;br /&gt;
The DREC (Diagnostics Recorder) is a tool used to send diagnostic requests onto the vehicle&#039;s communication buses and record the responses. The diagnostic requests can be provided in one of two ways:&lt;br /&gt;
&lt;br /&gt;
# By uploading a sequence file, where:&lt;br /&gt;
#* The sequence file contains one diagnostic request per line, with the ECU ID at the beginning of the line. Optionally, additional information may also be included. The syntax used for the sequence file is identical to that of the IDC module; for more details, refer to Sequence File Syntax.&lt;br /&gt;
# By selecting an existing IDC assignment.&lt;br /&gt;
&lt;br /&gt;
The output generated by DREC is a diagnostic log file, which is a text file containing both the requests (from the sequence file or IDC assignment) and their corresponding responses.&lt;br /&gt;
&lt;br /&gt;
====Recorder - SREC====&lt;br /&gt;
SREC (Signal recorder) is used to record signals on the vehicle&#039;s communication buses. The result of an SREC is an MDF file containing the time series data of the selected signals.&lt;br /&gt;
&lt;br /&gt;
For signal recorder there is 3 tabs: &lt;br /&gt;
&lt;br /&gt;
* Symbols - Add/Remove/view signals to record&lt;br /&gt;
* Frames - Handle frame recorder on Passive CAN and Flexray busses. &lt;br /&gt;
* Properties - Settings for the recorder. &lt;br /&gt;
&lt;br /&gt;
===== Symbols: =====&lt;br /&gt;
Buttons on the bottom strip:&lt;br /&gt;
&lt;br /&gt;
* Add Signal: Will open a window where signals can be added from. By selecting a signal source the list will be populated with signals available from that source.&lt;br /&gt;
* Remove selected: Selected signals will be removed. This is also possible by right click on the list.&lt;br /&gt;
* Edit Selected: To edit PLA-compressions (Read more [[PLA-compression window|here]].) and skip factor. Skip factor will be applied to all selected signals.&lt;br /&gt;
* More info: Shows more info about passive and Flexrays signals.&lt;br /&gt;
* Upload text file with signals names. If the signal does not have a module name it is expected to belong to the already selected signal source/module.&lt;br /&gt;
* Paste signals name to be added. If the signal does not have a module name it is expected to belong to the already selected signal source/module.&lt;br /&gt;
* Copy signals. In the new window it is possible to switch if it is only the filtered or all signals copied.  &lt;br /&gt;
[[File:Srec.png|none|thumb|955x955px]]&lt;br /&gt;
&lt;br /&gt;
====== Add Signals: ======&lt;br /&gt;
Click on the &#039;&#039;&#039;Add Signal&#039;&#039;&#039; button to show the window. Select modules/signal source and search up the signals that you want to add. Select those signals and click on &amp;quot;Add signals&amp;quot;.  &lt;br /&gt;
=====Recorder  - Properties=====&lt;br /&gt;
Under the recorder tab &#039;&#039;&#039;Properties&#039;&#039;&#039; you can select the properties for the recorder, see Figure &amp;quot;Recorder Properties&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Number of shots&#039;&#039;&#039; is an important factor for a recorder. A &#039;&#039;&#039;shot&#039;&#039;&#039; 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:&lt;br /&gt;
*The recording fulfills the maximum duration.&lt;br /&gt;
*The recording fulfills the minimum duration and the &#039;&#039;&#039;stop trigger condition&#039;&#039;&#039; is met.&lt;br /&gt;
*The recording fulfills the minimum duration and a trigger start a &#039;&#039;&#039;setup switch&#039;&#039;&#039;.&lt;br /&gt;
*The recording fulfills the minimum duration and another recorder starts a &#039;&#039;&#039;setup switch&#039;&#039;&#039;.&lt;br /&gt;
*A setup switch is started manually.&lt;br /&gt;
*The assignment is stopped manually.&lt;br /&gt;
The &#039;&#039;&#039;recorder Setup switch&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
You can also select the &#039;&#039;&#039;Pre trigg duration&#039;&#039;&#039; which determines the amount of data that will be saved in the flash before the start trigger condition is met. Range is 0 to 2147483647 (2&amp;lt;sup&amp;gt;31&amp;lt;/sup&amp;gt; -1).&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Post trigg duration&#039;&#039;&#039; 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 2147483647 (2&amp;lt;sup&amp;gt;31&amp;lt;/sup&amp;gt; -1).&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Minimum duration&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Maximum duration&#039;&#039;&#039; determines, as the name suggest, the maximum amount of data that should be recorded. Range is 0 to 2147483647 (2&amp;lt;sup&amp;gt;31&amp;lt;/sup&amp;gt; -1).&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Unit&#039;&#039;&#039; 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|link=https://wiki.alkit.se/wice264/index.php/File:Recorder_properties.png]]&lt;br /&gt;
&lt;br /&gt;
== Active signals ==&lt;br /&gt;
An Active Signal is a signal that is created by polling an ECU for a numerical value at a predefined frequency. The polling is typically done using the ReadDataByIdentifier diagnostic service. To create an assignment with active signals, the vehicle profile has to have a diagnostic description. This is set in the vehicle profile settings [[Vehicle Pofiles|here]]. There has to be a diagnostic description connected to the vehicle profile when the assignments are created to be able to select active signals. If a vehicle profile is updated, an assignment can be upgraded to match the new vehicle profile by doing a copy. This will automatically upgrade it and if there is a diagnostic description connected it will be possible to use active signals.&lt;br /&gt;
&lt;br /&gt;
Select “Active signal” in signal Source. Then it is possible to select ECU in ECU name. After that available signals will show up and select/deselect works like for the other signal sources.&lt;br /&gt;
&lt;br /&gt;
When creating a task with an assignment that has active signals selected, a button “ECU SW mappings” will show up. If there is a red exclamation mark, a specific software version has to be selected for one or more ECUs. If a recorder signal does not exist in the selected software version it will be removed. Note that the software version has to contain all active signals that exist in the trigger conditions otherwise it will not be possible to create the task.&lt;br /&gt;
==Using a portal assignment for a signal reader task==&lt;br /&gt;
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 &#039;&#039;&#039;Browse saved assignments&#039;&#039;&#039; button and select the assignment you want to use and click &#039;&#039;&#039;Ok&#039;&#039;&#039;. This assignment will now be used to create the .haf file required by the WCUs to perform the signal reader task. If selecting &amp;quot;Legacy WICE internal signal names&amp;quot; certain wice internal signals names will be translated. &lt;br /&gt;
[[File:BrowseSR.png|none|thumb|600x600px|View Assignments]]&lt;br /&gt;
Legacy WICE internal signal names:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! From&lt;br /&gt;
!To&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Longitude&lt;br /&gt;
|WICE_Generic_Internal.Longitude_0020&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Latitude&lt;br /&gt;
|WICE_Generic_Internal.Latitude_0020&lt;br /&gt;
|-&lt;br /&gt;
| WICE.CSQ&lt;br /&gt;
| WICE_Generic_Internal.CSQ_0020 &lt;br /&gt;
|-&lt;br /&gt;
|WICE.WCU_Voltage&lt;br /&gt;
|WICE_Generic_Internal.WCU_Voltage_0103&lt;br /&gt;
|-&lt;br /&gt;
|WICE.WCU_Temp&lt;br /&gt;
|WICE_Generic_Internal.WCU_Temp_0104&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Time_Since_Epoch&lt;br /&gt;
|WICE_Generic_Internal.Time_Since_Epoch_0090&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Start_Signal&lt;br /&gt;
|WICE_Generic_Internal.Start_Signal_0100&lt;br /&gt;
|}&lt;br /&gt;
== Select different communication interface or transport protocol ==&lt;br /&gt;
Under the &amp;quot;Modules&amp;quot; tab, the different signal sources are visible. In the &amp;quot;I/O&amp;quot; column, the selected communication interface and transport protocol are shown. By selecting a row and then clicking on the button “Edit Interface” this can be changed. Currently this is only possible for modules with type “A2L” or &amp;quot;Diagnostics.&amp;quot; When changing this, a validation of the settings with what is red from the corresponding A2L file is done. If the validation is successful, a green icon will appear. If the icon is a red cross the A2L file does not contain the necessary information for the setting.&lt;br /&gt;
&lt;br /&gt;
When selecting between CAN and Ethernet/DoIP diagnostics, a window pops up where you can select the interface between &amp;quot;Default Channel&amp;quot;, &amp;quot;CAN&amp;quot; or &amp;quot;DoIP&amp;quot;. Selecting &amp;quot;Default Channel&amp;quot; means that the default channel in the signal reader module settings on the wcu is going to be used. Interface &amp;quot;CAN&amp;quot; a specific CAN interface can be selected to be used for the diagnostic requests. If selecting &amp;quot;DoIP&amp;quot;, the diagnostics will be performed over Ethernet using the Diagnostics-over-IP (DoIP) protocol. In this case, you can also select whether to use the IP address broadcasted by the vehicle in a &amp;quot;Vehicle Announcement&amp;quot; message, or you can specify the IP address explicitly (in which case the Vehicle Announcement will be ignored). The DoIP port number to use (default 13400) can also be specified.&lt;br /&gt;
&lt;br /&gt;
A2L modules support the following interfaces, CPP-CAN, XCP-CAN, XCP-TCP, XCP-UDP and UDS (2C/2A).[[File:DoIP-ass-ed.png|alt=CAN or DoIP settings|thumb|CAN or DoIP settings|none]]&lt;br /&gt;
&lt;br /&gt;
== Record frames with filter ==&lt;br /&gt;
Frame recorder can be used on FlexRay and CAN-bus. In a signal recorder the frame recorder with or without filter can be activated. &lt;br /&gt;
&lt;br /&gt;
To activate/deactivate the frame recorder for a module either click on the active icon or select a specific row and click Toggle. &lt;br /&gt;
&lt;br /&gt;
To edit the filter either double click on row or click on edit filter.&lt;br /&gt;
[[File:Framerecorder.png|none|thumb|482x482px]]&lt;br /&gt;
&lt;br /&gt;
== Frame names in result file ==&lt;br /&gt;
If frame names should be included in the result file, this option can be enabled in the Modules tab. &lt;br /&gt;
&lt;br /&gt;
First, select the desired CAN bus, then click on &#039;Toggle Frame Names&#039; or simply check the &#039;Add Frame Names&#039; column. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note that this will increase the size of the result file.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== User defined signals ==&lt;br /&gt;
In this tab User Defined (UD) signals are handled. &lt;br /&gt;
&lt;br /&gt;
* Add and remove signals by clicking the respective button. &lt;br /&gt;
* Signal names are set on creation and can not be changed after that.&lt;br /&gt;
* Calculation formula is the formula that will be calculated for the UD signal&#039;s value. For example writing “module.signal_name + 10” will increase “signal_name” by 10. The calculatinon formula is based on [[Logical expressions]], [[Arithmetic expressions]] and [[Special expressions]]. &lt;br /&gt;
* Update on signals is determining when the formula shall be calculated. Each time that signals is read, the new user defined signal will be calculated.&lt;br /&gt;
&lt;br /&gt;
This type of signal can then be used in triggers and recorders by finding the name that will be “UD.&amp;lt;Name&amp;gt;”.&lt;br /&gt;
[[File:UD Editor2.png|none|thumb|483x483px]]&lt;br /&gt;
&lt;br /&gt;
== Import/Export assignment ==&lt;br /&gt;
Signal reader assignment can be exported and then be imported in another portal. Versions can mismatch with one version and still work. If it differs more, use it carefully. When importing an assignment and vehicle profile needs to be selected. This profile should be similar to that one the original assignment was based on. If some signals or signals source do not exist in the new profile that was used in assignment a warning message will be shown with information about what is missing. If missing signals were used in a trigger expression the state will be set as invalid. Today there is no way to export and import a vehicle profile. So these have to be done manually.&lt;br /&gt;
&lt;br /&gt;
== DAQ/Event-list ==&lt;br /&gt;
If the assignment contains signals source that are compatible with DAQ list or Event channels a tab with name “DAQ/Event” will be visible. After signals have been added to the recorder it can be added to the DAQ list.&lt;br /&gt;
&lt;br /&gt;
=== Add new DAQ-List ===&lt;br /&gt;
To add a new DAQ list click on green plus icon on specific Measurement setup and ECU name. The new window shows all the DAQ-list that was predefined in the a2l-file. &#039;&#039;&#039;NOTE! What information that will be shown depends on what transport protocol that is selected in the module settings.&#039;&#039;&#039; If there is no information the table will be empty. Choose either one from the list or select “New blank” to define DAQ-list yourself. &lt;br /&gt;
[[File:AddNewDAQ.png|none|thumb|528x528px]]&lt;br /&gt;
&lt;br /&gt;
=== Manage DAQ-List ===&lt;br /&gt;
On “Edit DAQ” following settings can be made: &lt;br /&gt;
&lt;br /&gt;
* Name&lt;br /&gt;
* DAQ number: Must be unique&lt;br /&gt;
* Periodicity: Will not affect the real periodicity is only for information.&lt;br /&gt;
* Max bytes/Max Frame: Depending on measurement is over can or ethernet. &lt;br /&gt;
* Prescaler&lt;br /&gt;
&lt;br /&gt;
[[File:DAQList.png|none|thumb|542x542px]]&lt;br /&gt;
&lt;br /&gt;
=== Manage Event channel ===&lt;br /&gt;
Manage event channels is similar to DAQ-list. In DAQ list you add signals but in event channels you add DAQ-list. With “Edit event” following settings can be made: &lt;br /&gt;
&lt;br /&gt;
* Name&lt;br /&gt;
* Channel number: Must be unique.&lt;br /&gt;
* Periodicity: Will not affect the real periodicity is only for information.&lt;br /&gt;
* Max DAQs: Note that 255 meaning infinity.&lt;br /&gt;
* Max Size of DAQs: Max byte each DAQ list can contain.&lt;br /&gt;
* Priority&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Assignment_Editor&amp;diff=4243</id>
		<title>Signal Reader Assignment Editor</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Assignment_Editor&amp;diff=4243"/>
		<updated>2026-09-09T11:12:24Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* User defined signals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Signal Reader Assignment Editor can be found under the tab &#039;&#039;&#039;Assignment&#039;&#039;&#039; and allows the user to create new assignments for signal reader directly in the portal. This page will guide you through the basics of using the editor.&lt;br /&gt;
&lt;br /&gt;
==Edit/Create a signal reader assignment==&lt;br /&gt;
&lt;br /&gt;
The first tab that you are presented with is the &#039;&#039;&#039;Assignment global settings&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
Under the &#039;&#039;&#039;Measurements&#039;&#039;&#039; tab, see Figure &amp;quot;Measurement Setups&amp;quot;, 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 &#039;&#039;&#039;Triggers&#039;&#039;&#039; that activate and deactivate on certain conditions provided by the user. Each trigger can contain a &#039;&#039;&#039;Recorder&#039;&#039;&#039; 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 &#039;&#039;&#039;setup switch&#039;&#039;&#039;.[[File:Measurement setup.png|none|thumb|608x608px|Measurement Setups]]&lt;br /&gt;
When you feel finished with the assignment you can simply click the &#039;&#039;&#039;Save assignment&#039;&#039;&#039; button in the lower right corner to save the assignment in its current state.&lt;br /&gt;
===Trigger===&lt;br /&gt;
To add a trigger to a measurement setup, click the &#039;&#039;&#039;plus&#039;&#039;&#039; 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. In the window, trigger type can be set to different types: Recorder, Setup switch, Pause diagnostics, Start/stop CCP DAQ, Start/stop XCP DAQ and Upload. With Setup switch you will jump/end/restart when the start condition is met.&lt;br /&gt;
&lt;br /&gt;
Fill out the &#039;&#039;&#039;start trigger&#039;&#039;&#039; &#039;&#039;&#039;condition&#039;&#039;&#039; for the trigger. This is easiest to do in the &#039;&#039;&#039;Edit expression&#039;&#039;&#039; window that you can get to by clicking one of the &#039;&#039;&#039;Edit&#039;&#039;&#039; buttons. To find a new signal to add a condition for, use the &#039;&#039;&#039;Add signal&#039;&#039;&#039; button. Here, you can browse all signals available for this assignment. Use the dropdown to browse signals from different can-busses and Wice internal signals. If you want to browse the signals currently in use in the assignment for the selected signal source, check the &#039;&#039;&#039;Search in assignment&#039;&#039;&#039; box. If you want more information about a signal, select it and click &#039;&#039;&#039;More info&#039;&#039;&#039;. When you have found the signal you want, double click it or select it and click &#039;&#039;&#039;Add signal&#039;&#039;&#039;. Now you can use the &#039;&#039;&#039;Operators&#039;&#039;&#039; list to add a condition for the signal, for example &amp;quot; &amp;gt; 0&amp;quot;. 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 &amp;quot;Validate Button States&amp;quot; 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|link=https://wiki.alkit.se/wice264/index.php/File:ValidateButtonStates.png|none]]A &#039;&#039;&#039;stop trigger condition&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
==== Speciel purpose trigger ====&lt;br /&gt;
&lt;br /&gt;
* Recorder&lt;br /&gt;
** Start Trigger - Start recording&lt;br /&gt;
** Stop Trigger - Stop recording&lt;br /&gt;
* Setup switch&lt;br /&gt;
** Start Trigger - Jumps to selected measurement setup&lt;br /&gt;
** Stop Trigger - N/A&lt;br /&gt;
* Pause diagnostics&lt;br /&gt;
** Start Trigger - Pauses sending of diagnostic requests&lt;br /&gt;
** Stop Trigger - Resumes sending of disgnostic requests&lt;br /&gt;
* Start/Stop CCP DAQ&lt;br /&gt;
** Start Trigger - Starts transmission of CCP DAQ lists&lt;br /&gt;
** Stop Trigger - Stops transmission of CCP DAQ lists&lt;br /&gt;
* Start/stop XCP DAQ&lt;br /&gt;
** Start Trigger - Starts transmission of XCP DAQ lists&lt;br /&gt;
** Stop Trigger - Stops transmission of XCP DAQ lists&lt;br /&gt;
* Upload&lt;br /&gt;
** Start Trigger - Will trigger to upload collected data to Portal&lt;br /&gt;
** Stop Trigger - N/A&lt;br /&gt;
* Vehicle ethernet&lt;br /&gt;
** Start Trigger - Activate vehicle ethernet&lt;br /&gt;
** Stop Trigger - Deactivate vehicle ethernet&lt;br /&gt;
&lt;br /&gt;
===Recorder===&lt;br /&gt;
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.&lt;br /&gt;
====Recorder - DREC====&lt;br /&gt;
DREC (Diagnostics recorder) is used to send diagnostic requests onto the vehicle&#039;s communication buses and record the responses. The diagnostic requests are supplied in a sequence file uploaded by the user. The sequence file contains one diagnostic request per line, with the ECU id at the beginning of the line. There can optionally be other information as well. The syntax is the same as the one used for the IDC module, see [[IDC Sequence File Syntax|Sequence File Syntax]]. The result from a DREC will be a diagnostic log file, a text file containing both the requests from the sequence file and the corresponding responses.&lt;br /&gt;
&lt;br /&gt;
The DREC (Diagnostics Recorder) is a tool used to send diagnostic requests onto the vehicle&#039;s communication buses and record the responses. The diagnostic requests can be provided in one of two ways:&lt;br /&gt;
&lt;br /&gt;
# By uploading a sequence file, where:&lt;br /&gt;
#* The sequence file contains one diagnostic request per line, with the ECU ID at the beginning of the line. Optionally, additional information may also be included. The syntax used for the sequence file is identical to that of the IDC module; for more details, refer to Sequence File Syntax.&lt;br /&gt;
# By selecting an existing IDC assignment.&lt;br /&gt;
&lt;br /&gt;
The output generated by DREC is a diagnostic log file, which is a text file containing both the requests (from the sequence file or IDC assignment) and their corresponding responses.&lt;br /&gt;
&lt;br /&gt;
====Recorder - SREC====&lt;br /&gt;
SREC (Signal recorder) is used to record signals on the vehicle&#039;s communication buses. The result of an SREC is an MDF file containing the time series data of the selected signals.&lt;br /&gt;
&lt;br /&gt;
For signal recorder there is 3 tabs: &lt;br /&gt;
&lt;br /&gt;
* Symbols - Add/Remove/view signals to record&lt;br /&gt;
* Frames - Handle frame recorder on Passive CAN and Flexray busses. &lt;br /&gt;
* Properties - Settings for the recorder. &lt;br /&gt;
&lt;br /&gt;
===== Symbols: =====&lt;br /&gt;
Buttons on the bottom strip:&lt;br /&gt;
&lt;br /&gt;
* Add Signal: Will open a window where signals can be added from. By selecting a signal source the list will be populated with signals available from that source.&lt;br /&gt;
* Remove selected: Selected signals will be removed. This is also possible by right click on the list.&lt;br /&gt;
* Edit Selected: To edit PLA-compressions (Read more [[PLA-compression window|here]].) and skip factor. Skip factor will be applied to all selected signals.&lt;br /&gt;
* More info: Shows more info about passive and Flexrays signals.&lt;br /&gt;
* Upload text file with signals names. If the signal does not have a module name it is expected to belong to the already selected signal source/module.&lt;br /&gt;
* Paste signals name to be added. If the signal does not have a module name it is expected to belong to the already selected signal source/module.&lt;br /&gt;
* Copy signals. In the new window it is possible to switch if it is only the filtered or all signals copied.  &lt;br /&gt;
[[File:Srec.png|none|thumb|955x955px]]&lt;br /&gt;
&lt;br /&gt;
====== Add Signals: ======&lt;br /&gt;
Click on the &#039;&#039;&#039;Add Signal&#039;&#039;&#039; button to show the window. Select modules/signal source and search up the signals that you want to add. Select those signals and click on &amp;quot;Add signals&amp;quot;.  &lt;br /&gt;
=====Recorder  - Properties=====&lt;br /&gt;
Under the recorder tab &#039;&#039;&#039;Properties&#039;&#039;&#039; you can select the properties for the recorder, see Figure &amp;quot;Recorder Properties&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Number of shots&#039;&#039;&#039; is an important factor for a recorder. A &#039;&#039;&#039;shot&#039;&#039;&#039; 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:&lt;br /&gt;
*The recording fulfills the maximum duration.&lt;br /&gt;
*The recording fulfills the minimum duration and the &#039;&#039;&#039;stop trigger condition&#039;&#039;&#039; is met.&lt;br /&gt;
*The recording fulfills the minimum duration and a trigger start a &#039;&#039;&#039;setup switch&#039;&#039;&#039;.&lt;br /&gt;
*The recording fulfills the minimum duration and another recorder starts a &#039;&#039;&#039;setup switch&#039;&#039;&#039;.&lt;br /&gt;
*A setup switch is started manually.&lt;br /&gt;
*The assignment is stopped manually.&lt;br /&gt;
The &#039;&#039;&#039;recorder Setup switch&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
You can also select the &#039;&#039;&#039;Pre trigg duration&#039;&#039;&#039; which determines the amount of data that will be saved in the flash before the start trigger condition is met. Range is 0 to 2147483647 (2&amp;lt;sup&amp;gt;31&amp;lt;/sup&amp;gt; -1).&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Post trigg duration&#039;&#039;&#039; 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 2147483647 (2&amp;lt;sup&amp;gt;31&amp;lt;/sup&amp;gt; -1).&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Minimum duration&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Maximum duration&#039;&#039;&#039; determines, as the name suggest, the maximum amount of data that should be recorded. Range is 0 to 2147483647 (2&amp;lt;sup&amp;gt;31&amp;lt;/sup&amp;gt; -1).&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;Unit&#039;&#039;&#039; 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|link=https://wiki.alkit.se/wice264/index.php/File:Recorder_properties.png]]&lt;br /&gt;
&lt;br /&gt;
== Active signals ==&lt;br /&gt;
An Active Signal is a signal that is created by polling an ECU for a numerical value at a predefined frequency. The polling is typically done using the ReadDataByIdentifier diagnostic service. To create an assignment with active signals, the vehicle profile has to have a diagnostic description. This is set in the vehicle profile settings [[Vehicle Pofiles|here]]. There has to be a diagnostic description connected to the vehicle profile when the assignments are created to be able to select active signals. If a vehicle profile is updated, an assignment can be upgraded to match the new vehicle profile by doing a copy. This will automatically upgrade it and if there is a diagnostic description connected it will be possible to use active signals.&lt;br /&gt;
&lt;br /&gt;
Select “Active signal” in signal Source. Then it is possible to select ECU in ECU name. After that available signals will show up and select/deselect works like for the other signal sources.&lt;br /&gt;
&lt;br /&gt;
When creating a task with an assignment that has active signals selected, a button “ECU SW mappings” will show up. If there is a red exclamation mark, a specific software version has to be selected for one or more ECUs. If a recorder signal does not exist in the selected software version it will be removed. Note that the software version has to contain all active signals that exist in the trigger conditions otherwise it will not be possible to create the task.&lt;br /&gt;
==Using a portal assignment for a signal reader task==&lt;br /&gt;
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 &#039;&#039;&#039;Browse saved assignments&#039;&#039;&#039; button and select the assignment you want to use and click &#039;&#039;&#039;Ok&#039;&#039;&#039;. This assignment will now be used to create the .haf file required by the WCUs to perform the signal reader task. If selecting &amp;quot;Legacy WICE internal signal names&amp;quot; certain wice internal signals names will be translated. &lt;br /&gt;
[[File:BrowseSR.png|none|thumb|600x600px|View Assignments]]&lt;br /&gt;
Legacy WICE internal signal names:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! From&lt;br /&gt;
!To&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Longitude&lt;br /&gt;
|WICE_Generic_Internal.Longitude_0020&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Latitude&lt;br /&gt;
|WICE_Generic_Internal.Latitude_0020&lt;br /&gt;
|-&lt;br /&gt;
| WICE.CSQ&lt;br /&gt;
| WICE_Generic_Internal.CSQ_0020 &lt;br /&gt;
|-&lt;br /&gt;
|WICE.WCU_Voltage&lt;br /&gt;
|WICE_Generic_Internal.WCU_Voltage_0103&lt;br /&gt;
|-&lt;br /&gt;
|WICE.WCU_Temp&lt;br /&gt;
|WICE_Generic_Internal.WCU_Temp_0104&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Time_Since_Epoch&lt;br /&gt;
|WICE_Generic_Internal.Time_Since_Epoch_0090&lt;br /&gt;
|-&lt;br /&gt;
|WICE.Start_Signal&lt;br /&gt;
|WICE_Generic_Internal.Start_Signal_0100&lt;br /&gt;
|}&lt;br /&gt;
== Select different communication interface or transport protocol ==&lt;br /&gt;
Under the &amp;quot;Modules&amp;quot; tab, the different signal sources are visible. In the &amp;quot;I/O&amp;quot; column, the selected communication interface and transport protocol are shown. By selecting a row and then clicking on the button “Edit Interface” this can be changed. Currently this is only possible for modules with type “A2L” or &amp;quot;Diagnostics.&amp;quot; When changing this, a validation of the settings with what is red from the corresponding A2L file is done. If the validation is successful, a green icon will appear. If the icon is a red cross the A2L file does not contain the necessary information for the setting.&lt;br /&gt;
&lt;br /&gt;
When selecting between CAN and Ethernet/DoIP diagnostics, a window pops up where you can select the interface between &amp;quot;Default Channel&amp;quot;, &amp;quot;CAN&amp;quot; or &amp;quot;DoIP&amp;quot;. Selecting &amp;quot;Default Channel&amp;quot; means that the default channel in the signal reader module settings on the wcu is going to be used. Interface &amp;quot;CAN&amp;quot; a specific CAN interface can be selected to be used for the diagnostic requests. If selecting &amp;quot;DoIP&amp;quot;, the diagnostics will be performed over Ethernet using the Diagnostics-over-IP (DoIP) protocol. In this case, you can also select whether to use the IP address broadcasted by the vehicle in a &amp;quot;Vehicle Announcement&amp;quot; message, or you can specify the IP address explicitly (in which case the Vehicle Announcement will be ignored). The DoIP port number to use (default 13400) can also be specified.&lt;br /&gt;
&lt;br /&gt;
A2L modules support the following interfaces, CPP-CAN, XCP-CAN, XCP-TCP, XCP-UDP and UDS (2C/2A).[[File:DoIP-ass-ed.png|alt=CAN or DoIP settings|thumb|CAN or DoIP settings|none]]&lt;br /&gt;
&lt;br /&gt;
== Record frames with filter ==&lt;br /&gt;
Frame recorder can be used on FlexRay and CAN-bus. In a signal recorder the frame recorder with or without filter can be activated. &lt;br /&gt;
&lt;br /&gt;
To activate/deactivate the frame recorder for a module either click on the active icon or select a specific row and click Toggle. &lt;br /&gt;
&lt;br /&gt;
To edit the filter either double click on row or click on edit filter.&lt;br /&gt;
[[File:Framerecorder.png|none|thumb|482x482px]]&lt;br /&gt;
&lt;br /&gt;
== Frame names in result file ==&lt;br /&gt;
If frame names should be included in the result file, this option can be enabled in the Modules tab. &lt;br /&gt;
&lt;br /&gt;
First, select the desired CAN bus, then click on &#039;Toggle Frame Names&#039; or simply check the &#039;Add Frame Names&#039; column. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note that this will increase the size of the result file.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== User defined signals ==&lt;br /&gt;
In this tab User Defined (UD) signals are handled. &lt;br /&gt;
&lt;br /&gt;
* Add and remove signals by clicking the respective button. &lt;br /&gt;
* Signal names are set on creation and can not be changed after that.&lt;br /&gt;
* Calculation formula is the formula that will be calculated for the UD signal&#039;s value. For example writing “module.signal_name + 10” will increase “signal_name” by 10. The calculatinon formula is based on [[Logical expressions]], [[Arithmetic expressions]] and [[Special expressions]]. &lt;br /&gt;
* Update on signals is determining when the formula shall be calculated. Each time that signals is read, the new user defined signal will be calculated.&lt;br /&gt;
&lt;br /&gt;
This type of signal can then be used in triggers and recorders by finding the name that will be “UD.&amp;lt;Name&amp;gt;”.&lt;br /&gt;
[[File:UD Editor2.png|none|thumb|483x483px]]&lt;br /&gt;
&lt;br /&gt;
== Import/Export assignment ==&lt;br /&gt;
Signal reader assignment can be exported and then be imported in another portal. Versions can mismatch with one version and still work. If it differs more, use it carefully. When importing an assignment and vehicle profile needs to be selected. This profile should be similar to that one the original assignment was based on. If some signals or signals source do not exist in the new profile that was used in assignment a warning message will be shown with information about what is missing. If missing signals were used in a trigger expression the state will be set as invalid. Today there is no way to export and import a vehicle profile. So these have to be done manually.&lt;br /&gt;
&lt;br /&gt;
== DAQ/Event-list ==&lt;br /&gt;
If the assignment contains signals source that are compatible with DAQ list or Event channels a tab with name “DAQ/Event” will be visible. After signals have been added to the recorder it can be added to the DAQ list.&lt;br /&gt;
&lt;br /&gt;
=== Add new DAQ-List ===&lt;br /&gt;
To add a new DAQ list click on green plus icon on specific Measurement setup and ECU name. The new window shows all the DAQ-list that was predefined in the a2l-file. &#039;&#039;&#039;NOTE! What information that will be shown depends on what transport protocol that is selected in the module settings.&#039;&#039;&#039; If there is no information the table will be empty. Choose either one from the list or select “New blank” to define DAQ-list yourself. &lt;br /&gt;
[[File:AddNewDAQ.png|none|thumb|528x528px]]&lt;br /&gt;
&lt;br /&gt;
=== Manage DAQ-List ===&lt;br /&gt;
On “Edit DAQ” following settings can be made: &lt;br /&gt;
&lt;br /&gt;
* Name&lt;br /&gt;
* DAQ number: Must be unique&lt;br /&gt;
* Periodicity: Will not affect the real periodicity is only for information.&lt;br /&gt;
* Max bytes/Max Frame: Depending on measurement is over can or ethernet. &lt;br /&gt;
* Prescaler&lt;br /&gt;
&lt;br /&gt;
[[File:DAQList.png|none|thumb|542x542px]]&lt;br /&gt;
&lt;br /&gt;
=== Manage Event channel ===&lt;br /&gt;
Manage event channels is similar to DAQ-list. In DAQ list you add signals but in event channels you add DAQ-list. With “Edit event” following settings can be made: &lt;br /&gt;
&lt;br /&gt;
* Name&lt;br /&gt;
* Channel number: Must be unique.&lt;br /&gt;
* Periodicity: Will not affect the real periodicity is only for information.&lt;br /&gt;
* Max DAQs: Note that 255 meaning infinity.&lt;br /&gt;
* Max Size of DAQs: Max byte each DAQ list can contain.&lt;br /&gt;
* Priority&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Special_expressions&amp;diff=4242</id>
		<title>Special expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Special_expressions&amp;diff=4242"/>
		<updated>2026-09-09T11:06:45Z</updated>

		<summary type="html">&lt;p&gt;Mathias: Created page with &amp;quot;The following special expressions are supported in User Defined signals. Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed. Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.  {|...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following special expressions are supported in User Defined signals.&lt;br /&gt;
Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|-&lt;br /&gt;
!NO_SIGNAL&lt;br /&gt;
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL(&#039;Signal&#039;, &#039;Numeric Value&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_SINCE_UPDATE&lt;br /&gt;
|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE(&#039;Signal&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!IF-THEN-ELSE&lt;br /&gt;
|Conditional. Syntax: IF boolean expression THEN expression ELSE expression&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Logical_expressions&amp;diff=4241</id>
		<title>Logical expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Logical_expressions&amp;diff=4241"/>
		<updated>2026-09-09T08:55:05Z</updated>

		<summary type="html">&lt;p&gt;Mathias: Created page with &amp;quot;Logical (or boolean) expressions consists of a combination of logical operations which can be grouped by parentheses. The supported logical operators are as follows.  {| class=&amp;quot;wikitable&amp;quot; != |Tests for equality. Syntax: expression = expression |- !!= |Tests for inequality. Syntax: expression != expression |- !&amp;lt; |Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression |- !&amp;gt; |Tests for left side of expression being greater than right s...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Logical (or boolean) expressions consists of a combination of logical operations which can be grouped by parentheses. The supported logical operators are as follows.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Arithmetic_expressions&amp;diff=4240</id>
		<title>Arithmetic expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Arithmetic_expressions&amp;diff=4240"/>
		<updated>2026-09-09T08:47:09Z</updated>

		<summary type="html">&lt;p&gt;Mathias: Arithmetic expressions&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Arithmetic expressions contain one or more arithmetic operations which can be grouped by parentheses. The supported arithmetic operators are as follows.&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Operator&lt;br /&gt;
!Description&lt;br /&gt;
!Syntax&lt;br /&gt;
!Example&lt;br /&gt;
|-&lt;br /&gt;
|*&lt;br /&gt;
|Multiplication&lt;br /&gt;
|operand1 * operand2&lt;br /&gt;
|CAN.Signal1 * 3.14&lt;br /&gt;
|-&lt;br /&gt;
|/&lt;br /&gt;
|Division&lt;br /&gt;
|operand1 / operand2&lt;br /&gt;
|CAN.Signal1 / 2&lt;br /&gt;
|-&lt;br /&gt;
| +&lt;br /&gt;
|Addition&lt;br /&gt;
|operand1 + operand2&lt;br /&gt;
|CAN.Signal1 + 2&lt;br /&gt;
|-&lt;br /&gt;
| -&lt;br /&gt;
|Subtraction&lt;br /&gt;
|operand1 - operand2&lt;br /&gt;
|CAN.Signal1 - CAN.Signal2&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Bitwise_expressions&amp;diff=4239</id>
		<title>Bitwise expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Bitwise_expressions&amp;diff=4239"/>
		<updated>2026-09-09T08:41:49Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A bitwise expression consists of one or more bitwise operators which can be grouped by parentheses.The following bitwise operators are supported:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Operator&lt;br /&gt;
!Description&lt;br /&gt;
!Syntax&lt;br /&gt;
!Example&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;|&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|Bitwise OR&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;operand1 | operand2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;CAN1.EnginState | 1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;amp;&lt;br /&gt;
|Bitwise AND&lt;br /&gt;
|operand1 &amp;amp; operand2&lt;br /&gt;
|CAN1.EnginState &amp;amp; 1&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Bitwise_expressions&amp;diff=4238</id>
		<title>Bitwise expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Bitwise_expressions&amp;diff=4238"/>
		<updated>2026-09-09T08:37:29Z</updated>

		<summary type="html">&lt;p&gt;Mathias: Bitwise expressions&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A bitwise expression consists of one or more bitwise operators which can be grouped by parentheses.The following bitwise operators are supported:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+&lt;br /&gt;
!Operator&lt;br /&gt;
!Description&lt;br /&gt;
!Syntac&lt;br /&gt;
!Example&lt;br /&gt;
|-&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;|&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|Bitwise OR&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;operand1 | operand2&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|&amp;lt;nowiki&amp;gt;CAN1.EnginState | 1&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&amp;amp;&lt;br /&gt;
|Bitwise AND&lt;br /&gt;
|operand1 &amp;amp; operand2&lt;br /&gt;
|CAN1.EnginState &amp;amp; 1&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.99&amp;diff=4237</id>
		<title>New features in v2.99</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.99&amp;diff=4237"/>
		<updated>2026-09-08T14:16:07Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== New special purpose trigger for Signal Reader assignments ==&lt;br /&gt;
New trigger type in Signal reader assignment, Vehicle Ethernet. Start trigger will activate ethernet. Stop trigger will deactivate ethernet. Read more [[Signal Reader Assignment Editor#Speciel purpose trigger|here.]]&lt;br /&gt;
&lt;br /&gt;
== WICE internal signals Platform and version validation ==&lt;br /&gt;
WICE internal signals now have validation that the WCU has the correct version and platform when creating new signal reader tasks. If a signal reader assignment contains signals that are not supported on all platforms a warning will show when saving the assignment. The warning will show all affected signals and the platform they will support. If an assignment is created on a WCU with a platform/version that not all signals are supported in the assignment a warning message will warn the user for this, but currently not say wish signal. &lt;br /&gt;
&lt;br /&gt;
== New WICE internal signals for ethernet carrier ==&lt;br /&gt;
New WICE internal signals: WICE.Ethernet_Interface_Status_0 and WICE.Ethernet_Interface_Status_1. Is the Ethernet carrier on eth0 and eth1. 0 - no ethernet connected. 1  - ethernet connected.&lt;br /&gt;
&lt;br /&gt;
== Support new attributes from LDM - TCPXRef ==&lt;br /&gt;
New attributes supports from LDM:&lt;br /&gt;
&lt;br /&gt;
* SiteName&lt;br /&gt;
* tt_responsible&lt;br /&gt;
* vehicleContact&lt;br /&gt;
* projectLabel&lt;br /&gt;
* tsu        &lt;br /&gt;
* vin&lt;br /&gt;
* chassisNo&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports  DoIP Alive Check ==&lt;br /&gt;
Signal Reader responds to a DoIP Alive Check requests with an Alive Check response to keep an ongoing DoIP session active.&lt;br /&gt;
&lt;br /&gt;
== Improved timer-based triggers in Signal Reader ==&lt;br /&gt;
Timer based triggers evaluated separately for start and stop conditions. This avoids problems with for instance NO_SIGNAL and LOSS_OF_SIGNAL based triggers.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.99&amp;diff=4236</id>
		<title>New features in v2.99</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.99&amp;diff=4236"/>
		<updated>2026-09-08T14:12:01Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== New special purpose trigger for Signal Reader assignments ==&lt;br /&gt;
New trigger type in Signal reader assignment, Vehicle Ethernet. Start trigger will activate ethernet. Stop trigger will deactivate ethernet. Read more [[Signal Reader Assignment Editor#Speciel purpose trigger|here.]]&lt;br /&gt;
&lt;br /&gt;
== WICE internal signals Platform and version validation ==&lt;br /&gt;
WICE internal signals now have validation that the WCU has the correct version and platform when creating new signal reader tasks. If a signal reader assignment contains signals that are not supported on all platforms a warning will show when saving the assignment. The warning will show all affected signals and the platform they will support. If an assignment is created on a WCU with a platform/version that not all signals are supported in the assignment a warning message will warn the user for this, but currently not say wish signal. &lt;br /&gt;
&lt;br /&gt;
== New WICE internal signals for ethernet carrier ==&lt;br /&gt;
New WICE internal signals: WICE.Ethernet_Interface_Status_0 and WICE.Ethernet_Interface_Status_1. Is the Ethernet carrier on eth0 and eth1. 0 - no ethernet connected. 1  - ethernet connected.&lt;br /&gt;
&lt;br /&gt;
== Support new attributes from LDM - TCPXRef ==&lt;br /&gt;
New attributes supports from LDM:&lt;br /&gt;
&lt;br /&gt;
* SiteName&lt;br /&gt;
* tt_responsible&lt;br /&gt;
* vehicleContact&lt;br /&gt;
* projectLabel&lt;br /&gt;
* tsu        &lt;br /&gt;
* vin&lt;br /&gt;
* chassisNo&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports  DoIP Alive Check ==&lt;br /&gt;
Signal Reader responds to a DoIP Alive Check requests with an Alive Check response to keep an ongoing DoIP session active.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4211</id>
		<title>Signal Reader Trigger Expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4211"/>
		<updated>2026-05-21T07:14:58Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE&lt;br /&gt;
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP&lt;br /&gt;
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN&lt;br /&gt;
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_BY&lt;br /&gt;
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP_BY&lt;br /&gt;
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN_BY&lt;br /&gt;
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_FROM_TO&lt;br /&gt;
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)&lt;br /&gt;
|-&lt;br /&gt;
!TIMER&lt;br /&gt;
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)&lt;br /&gt;
|-&lt;br /&gt;
!EXPR_TIMER&lt;br /&gt;
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!EVERY&lt;br /&gt;
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)&lt;br /&gt;
|-&lt;br /&gt;
!MOVAV&lt;br /&gt;
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|-&lt;br /&gt;
!NO_SIGNAL&lt;br /&gt;
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL(&#039;Signal&#039;, &#039;Numeric Value&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_SINCE_UPDATE&lt;br /&gt;
|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE(&#039;Signal&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!DM1&lt;br /&gt;
|Returns the FMI value of a specified ECU&#039;s J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN), where ECU-id should be i hexadecimal, e.g. 0x10.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4210</id>
		<title>New features in v2.98</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4210"/>
		<updated>2026-05-21T07:08:46Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Show existing PINs for resource groups ==&lt;br /&gt;
&lt;br /&gt;
== Enable fetching PINs from PIE for individual vehicles ==&lt;br /&gt;
&lt;br /&gt;
== Resource group WMUs ==&lt;br /&gt;
&lt;br /&gt;
== Add reported WMU to WCU&#039;s WMU configuration ==&lt;br /&gt;
&lt;br /&gt;
== Permission to control edit of WCUs and Vehicles. ==&lt;br /&gt;
Starting from version 2.98.0, administrators can assign new permissions that determine whether a user can edit a WCU or a vehicle. In the portal, these permissions are called &#039;&#039;&#039;WCU View Permission&#039;&#039;&#039; (&amp;lt;code&amp;gt;wcu:view:write&amp;lt;/code&amp;gt;) for WCUs and &#039;&#039;&#039;Vehicle Edit Permission&#039;&#039;&#039; (&amp;lt;code&amp;gt;vehicle:view:write&amp;lt;/code&amp;gt;) for vehicles. Read more about it [[Roles and permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Add or revoke permissions to existing tasks ==&lt;br /&gt;
The options to add or revoke permissions to existing tasks have been improved from version 2.98. In summary, when removing a WCU from a permission either by removing it as resource from the permission itself, or by removing it from the resource group used in the permission or by removing the permission label from the resource, access to existing tasks can also be removed. More information and example can be found in [[Roles and permissions#Permission for specific tasks]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports LIN frame logging in MDF4 format ==&lt;br /&gt;
Signal Reader now supports LIN frame logging in MDF4 format in addition to ASC format. The setting for whether to use MDF4 or ASC is the same as for CAN frame logging, in the Signal Reader module configuration.&lt;br /&gt;
&lt;br /&gt;
== New trigger expression for DM1 Diagnostic Trouble Codes in Signal Reader ==&lt;br /&gt;
A new type of trigger expression makes it possible to react DM1 DTC, by triggering on ECU id, SPN and FMI. For more information, see [[Signal Reader Trigger Expressions]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports channel mapping as meta information for frame logs ==&lt;br /&gt;
When logging CAN and LIN frames in MDF4, meta-information is added to the output file describing the mapping of the CAN/LIN buses.&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports MDF4 Event Blocks for frame logs ==&lt;br /&gt;
Signal Reader can now generate MDF4 Event Blocks for frame logs in the same way as for signal logs. This makes it easier to correlate frame logs and signal logs (and other data) in post-processing operations.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4209</id>
		<title>Signal Reader Trigger Expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4209"/>
		<updated>2026-05-21T07:06:54Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE&lt;br /&gt;
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP&lt;br /&gt;
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN&lt;br /&gt;
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_BY&lt;br /&gt;
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP_BY&lt;br /&gt;
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN_BY&lt;br /&gt;
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_FROM_TO&lt;br /&gt;
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)&lt;br /&gt;
|-&lt;br /&gt;
!TIMER&lt;br /&gt;
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)&lt;br /&gt;
|-&lt;br /&gt;
!EXPR_TIMER&lt;br /&gt;
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!EVERY&lt;br /&gt;
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)&lt;br /&gt;
|-&lt;br /&gt;
!MOVAV&lt;br /&gt;
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|-&lt;br /&gt;
!NO_SIGNAL&lt;br /&gt;
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL(&#039;Signal&#039;, &#039;Numeric Value&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_SINCE_UPDATE&lt;br /&gt;
|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE(&#039;Signal&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!DM1&lt;br /&gt;
|Returns the FMI value of a specified ECU&#039;s J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4208</id>
		<title>Signal Reader Trigger Expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4208"/>
		<updated>2026-05-21T07:05:32Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE&lt;br /&gt;
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP&lt;br /&gt;
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN&lt;br /&gt;
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_BY&lt;br /&gt;
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP_BY&lt;br /&gt;
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN_BY&lt;br /&gt;
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_FROM_TO&lt;br /&gt;
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)&lt;br /&gt;
|-&lt;br /&gt;
!TIMER&lt;br /&gt;
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)&lt;br /&gt;
|-&lt;br /&gt;
!EXPR_TIMER&lt;br /&gt;
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!EVERY&lt;br /&gt;
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)&lt;br /&gt;
|-&lt;br /&gt;
!MOVAV&lt;br /&gt;
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|-&lt;br /&gt;
!NO_SIGNAL&lt;br /&gt;
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL(&#039;Signal&#039;, &#039;Numeric Value&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_SINCE_UPDATE&lt;br /&gt;
|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE(&#039;Signal&#039;)&lt;br /&gt;
!DM1&lt;br /&gt;
|Returns the FMI value of a specified ECU&#039;s J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4207</id>
		<title>Signal Reader Trigger Expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4207"/>
		<updated>2026-05-21T07:04:33Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE&lt;br /&gt;
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP&lt;br /&gt;
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN&lt;br /&gt;
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_BY&lt;br /&gt;
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP_BY&lt;br /&gt;
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN_BY&lt;br /&gt;
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_FROM_TO&lt;br /&gt;
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)&lt;br /&gt;
|-&lt;br /&gt;
!DM1&lt;br /&gt;
|Returns the FMI value of a specified ECU&#039;s J1939 DM1 message with the specified SPN. Syntax: DM1(ECU-id, SPN)&lt;br /&gt;
|-&lt;br /&gt;
!TIMER&lt;br /&gt;
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)&lt;br /&gt;
|-&lt;br /&gt;
!EXPR_TIMER&lt;br /&gt;
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!EVERY&lt;br /&gt;
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)&lt;br /&gt;
|-&lt;br /&gt;
!MOVAV&lt;br /&gt;
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|-&lt;br /&gt;
!NO_SIGNAL&lt;br /&gt;
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL(&#039;Signal&#039;, &#039;Numeric Value&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_SINCE_UPDATE&lt;br /&gt;
|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE(&#039;Signal&#039;)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4203</id>
		<title>New features in v2.98</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4203"/>
		<updated>2026-05-21T06:49:31Z</updated>

		<summary type="html">&lt;p&gt;Mathias: framelog mf4 event block&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Show existing PINs for resource groups ==&lt;br /&gt;
&lt;br /&gt;
== Enable fetching PINs from PIE for individual vehicles ==&lt;br /&gt;
&lt;br /&gt;
== Resource group WMUs ==&lt;br /&gt;
&lt;br /&gt;
== Add reported WMU to WCU&#039;s WMU configuration ==&lt;br /&gt;
&lt;br /&gt;
== Permission to control edit of WCUs. ==&lt;br /&gt;
Starting from version 2.98.0, administrators can assign a new permission that determines whether a user can edit a WCU. In the portal the permission is called &amp;quot;WCU View Permission&amp;quot; (wcu:view:write). Read more about it [[Roles and permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Add or revoke permissions to existing tasks ==&lt;br /&gt;
The options to add or revoke permissions to existing tasks have been improved from version 2.98. In summary, when removing a WCU from a permission either by removing it as resource from the permission itself, or by removing it from the resource group used in the permission or by removing the permission label from the resource, access to existing tasks can also be removed. More information and example can be found in [[Roles and permissions#Permission for specific tasks]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports LIN frame logging in MDF4 format ==&lt;br /&gt;
Signal Reader now supports LIN frame logging in MDF4 format in addition to ASC format. The setting for whether to use MDF4 or ASC is the same as for CAN frame logging, in the Signal Reader module configuration.&lt;br /&gt;
&lt;br /&gt;
== New trigger expression for DM1 Diagnostic Trouble Codes in Signal Reader ==&lt;br /&gt;
A new type of trigger expression makes it possible to react DM1 DTC, by triggering on ECU id, SPN and FMI.&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports channel mapping as meta information for frame logs ==&lt;br /&gt;
When logging CAN and LIN frames in MDF4, meta-information is added to the output file describing the mapping of the CAN/LIN buses.&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports MDF4 Event Blocks for frame logs ==&lt;br /&gt;
Signal Reader can now generate MDF4 Event Blocks for frame logs in the same way as for signal logs. This makes it easier to correlate frame logs and signal logs (and other data) in post-processing operations.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4202</id>
		<title>New features in v2.98</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4202"/>
		<updated>2026-05-21T06:43:38Z</updated>

		<summary type="html">&lt;p&gt;Mathias: DM1 Triggers&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Show existing PINs for resource groups ==&lt;br /&gt;
&lt;br /&gt;
== Enable fetching PINs from PIE for individual vehicles ==&lt;br /&gt;
&lt;br /&gt;
== Resource group WMUs ==&lt;br /&gt;
&lt;br /&gt;
== Add reported WMU to WCU&#039;s WMU configuration ==&lt;br /&gt;
&lt;br /&gt;
== Permission to control edit of WCUs. ==&lt;br /&gt;
Starting from version 2.98.0, administrators can assign a new permission that determines whether a user can edit a WCU. In the portal the permission is called &amp;quot;WCU View Permission&amp;quot; (wcu:view:write). Read more about it [[Roles and permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Add or revoke permissions to existing tasks ==&lt;br /&gt;
The options to add or revoke permissions to existing tasks have been improved from version 2.98. In summary, when removing a WCU from a permission either by removing it as resource from the permission itself, or by removing it from the resource group used in the permission or by removing the permission label from the resource, access to existing tasks can also be removed. More information and example can be found in [[Roles and permissions#Permission for specific tasks]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports LIN frame logging in MDF4 format ==&lt;br /&gt;
Signal Reader now supports LIN frame logging in MDF4 format in addition to ASC format. The setting for whether to use MDF4 or ASC is the same as for CAN frame logging, in the Signal Reader module configuration.&lt;br /&gt;
&lt;br /&gt;
== New trigger expression for DM1 Diagnostic Trouble Codes in Signal Reader ==&lt;br /&gt;
A new type of trigger expression makes it possible to react DM1 DTC, by triggering on ECU id, SPN and FMI.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4200</id>
		<title>New features in v2.98</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.98&amp;diff=4200"/>
		<updated>2026-05-21T06:40:23Z</updated>

		<summary type="html">&lt;p&gt;Mathias: LIN MDF4&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Show existing PINs for resource groups ==&lt;br /&gt;
&lt;br /&gt;
== Enable fetching PINs from PIE for individual vehicles ==&lt;br /&gt;
&lt;br /&gt;
== Resource group WMUs ==&lt;br /&gt;
&lt;br /&gt;
== Add reported WMU to WCU&#039;s WMU configuration ==&lt;br /&gt;
&lt;br /&gt;
== Permission to control edit of WCUs. ==&lt;br /&gt;
Starting from version 2.98.0, administrators can assign a new permission that determines whether a user can edit a WCU. Read more about it here.&lt;br /&gt;
&lt;br /&gt;
== Add or revoke permissions to existing tasks ==&lt;br /&gt;
The options to add or revoke permissions to existing tasks have been improved from version 2.98. In summary, when removing a WCU from a permission either by removing it as resource from the permission itself, or by removing it from the resource group used in the permission or by removing the permission label from the resource, access to existing tasks can also be removed. More information and example can be found in [[Roles and permissions#Permission for specific tasks]].&lt;br /&gt;
&lt;br /&gt;
== Signal Reader supports LIN frame logging in MDF4 format ==&lt;br /&gt;
Signal Reader now supports LIN frame logging in MDF4 format in addition to ASC format. The setting for whether to use MDF4 or ASC is the same as for CAN frame logging, in the Signal Reader module configuration.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.97&amp;diff=4146</id>
		<title>New features in v2.97</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.97&amp;diff=4146"/>
		<updated>2026-02-19T10:19:13Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Add all signals and multiple signal sources for signal reader in the assignment editor. ==&lt;br /&gt;
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.&lt;br /&gt;
&lt;br /&gt;
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.&lt;br /&gt;
&lt;br /&gt;
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.&lt;br /&gt;
&lt;br /&gt;
== Support for WCU hardened mode. ==&lt;br /&gt;
WCU Hardened Mode indicates that a WCU meets the customer-specific requirements in the Module and Configuration settings. When the requirements are fulfilled, the WCU is marked with a system label named “wcu_hardened.”&lt;br /&gt;
&lt;br /&gt;
If Hardened Mode is enabled in the current environment, two buttons are available in both Edit Configuration and Modules. These provide an overview of the required settings and clearly show what is missing for the current WCU to meet the Hardened Mode requirements.&lt;br /&gt;
&lt;br /&gt;
== Support for automatically generating passwords ==&lt;br /&gt;
Admins can now automatically generate a new password for a user directly from the User panel’s Change Password dialog. Learn more [[The Portal Administrator View#The User Tab|here]].&lt;br /&gt;
&lt;br /&gt;
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==&lt;br /&gt;
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: &#039;&#039;&#039;Role&#039;&#039;&#039; and &#039;&#039;&#039;Speed&#039;&#039;&#039;. For automotive Ethernet channels, only the &#039;&#039;&#039;Static&#039;&#039;&#039; addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].&lt;br /&gt;
&lt;br /&gt;
== Configurable default time interval for alarms in portal ==&lt;br /&gt;
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the &#039;&#039;&#039;Active Alarms&#039;&#039;&#039; column in the &#039;&#039;&#039;Vehicles&#039;&#039;&#039; tab or by navigating to the &#039;&#039;&#039;Alarms&#039;&#039;&#039; tab in &#039;&#039;&#039;Administration&#039;&#039;&#039; and clicking the &#039;&#039;&#039;Set Alarm Interval&#039;&#039;&#039; button. Read more [[Alarm#Set Alarm Interval|here]].&lt;br /&gt;
&lt;br /&gt;
== Improvements to Creating/View Mapping on Signal Reader Task ==&lt;br /&gt;
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]&lt;br /&gt;
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]&lt;br /&gt;
The Signal Reader task view has been improved to display the mapped-from and mapped-to names for better clarity. It also shows the mapping type, which can be WCU, WMU, or MRCOM, making it easier to identify which mapping type the CAN/LIN is assigned to. &lt;br /&gt;
&lt;br /&gt;
The process of creating a Signal Reader task has also been enhanced to include additional information. It now indicates whether the CAN is sourced from a mapping type of WCU, WMU, or MRCOM. For a clearer example, refer to the image &#039;Signal Reader Create Mapping&#039;.&amp;quot; To read more about this, [[Mappings|click here]].&lt;br /&gt;
&lt;br /&gt;
== Improved timestamping in Signal Reader ==&lt;br /&gt;
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.97&amp;diff=4145</id>
		<title>New features in v2.97</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.97&amp;diff=4145"/>
		<updated>2026-02-19T10:18:24Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Add all signals and multiple signal sources for signal reader in the assignment editor. ==&lt;br /&gt;
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.&lt;br /&gt;
&lt;br /&gt;
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.&lt;br /&gt;
&lt;br /&gt;
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.&lt;br /&gt;
&lt;br /&gt;
== Support for WCU hardened mode. ==&lt;br /&gt;
WCU Hardened Mode indicates that a WCU meets the customer-specific requirements in the Module and Configuration settings. When the requirements are fulfilled, the WCU is marked with a system label named “wcu_hardened.”&lt;br /&gt;
&lt;br /&gt;
If Hardened Mode is enabled in the current environment, two buttons are available in both Edit Configuration and Modules. These provide an overview of the required settings and clearly show what is missing for the current WCU to meet the Hardened Mode requirements.&lt;br /&gt;
&lt;br /&gt;
== Support for automatically generating passwords ==&lt;br /&gt;
Admins can now automatically generate a new password for a user directly from the User panel’s Change Password dialog. Learn more [[The Portal Administrator View#The User Tab|here]].&lt;br /&gt;
&lt;br /&gt;
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==&lt;br /&gt;
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: &#039;&#039;&#039;Role&#039;&#039;&#039; and &#039;&#039;&#039;Speed&#039;&#039;&#039;. For automotive Ethernet channels, only the &#039;&#039;&#039;Static&#039;&#039;&#039; addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].&lt;br /&gt;
&lt;br /&gt;
== Configurable default time interval for alarms in portal ==&lt;br /&gt;
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the &#039;&#039;&#039;Active Alarms&#039;&#039;&#039; column in the &#039;&#039;&#039;Vehicles&#039;&#039;&#039; tab or by navigating to the &#039;&#039;&#039;Alarms&#039;&#039;&#039; tab in &#039;&#039;&#039;Administration&#039;&#039;&#039; and clicking the &#039;&#039;&#039;Set Alarm Interval&#039;&#039;&#039; button. Read more [[Alarm#Set Alarm Interval|here]].&lt;br /&gt;
&lt;br /&gt;
== Improvements to Creating/View Mapping on Signal Reader Task ==&lt;br /&gt;
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]&lt;br /&gt;
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]&lt;br /&gt;
The Signal Reader task view has been improved to display the mapped-from and mapped-to names for better clarity. It also shows the mapping type, which can be WCU, WMU, or MRCOM, making it easier to identify which mapping type the CAN/LIN is assigned to. &lt;br /&gt;
&lt;br /&gt;
The process of creating a Signal Reader task has also been enhanced to include additional information. It now indicates whether the CAN is sourced from a mapping type of WCU, WMU, or MRCOM. For a clearer example, refer to the image &#039;Signal Reader Create Mapping&#039;.&amp;quot; To read more about this, [[Mappings|click here]].&lt;br /&gt;
&lt;br /&gt;
== Improved time-stamping in Signal Reader ==&lt;br /&gt;
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.96&amp;diff=4100</id>
		<title>New features in v2.96</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.96&amp;diff=4100"/>
		<updated>2025-11-11T08:04:52Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.&lt;br /&gt;
&lt;br /&gt;
== DLT Daemon mode and DLT UDS in parallel ==&lt;br /&gt;
The portal now supports creating DLT tasks with daemon mode and UDS service 38 enabled at the same time. This requires WCU software version 2.96.0 or later for the selected WCUs. See [[Creating a Task#Diagnostic Log and Trace (DLT)|Creating a Task#Diagnostic Log and Trace (DLT).]]&lt;br /&gt;
&lt;br /&gt;
== DLT Daemon address via vehicle announcement ==&lt;br /&gt;
For WCUs configured for software version 2.96.0 it is possible to get the daemon address via vehicle announcement instead of specifying a daemon address when the task is created. See [[Creating a Task#Diagnostic Log and Trace (DLT)|Creating a Task#Diagnostic Log and Trace (DLT).]]&lt;br /&gt;
&lt;br /&gt;
== Set, View, and Apply Default WCU Configurations ==&lt;br /&gt;
Starting from version 2.96, users can now set, view, and apply default WCU configurations. Admin permissions are required to access these new functions. Read more about it [[Default WCU Configuration|here]].&lt;br /&gt;
&lt;br /&gt;
== Users can now shelve a WCU directly from the Vehicles panel ==&lt;br /&gt;
Users with WCU shelving permissions can now shelve a WCU directly in the Vehicles panel. Read more about it [[Shelve and Unshelve a WCU|here]].&lt;br /&gt;
&lt;br /&gt;
== VINReader option to not request VIN if known ==&lt;br /&gt;
A new option is available to silence VINReader on startup if the VIN is already known. When in play, VINReader will stay silent, i.e. not request any VIN, if VIN is already known. However, if VIN is unknown, VINReader will send a request for VIN.&lt;br /&gt;
&lt;br /&gt;
== Support for diagnostic Build ID request ==&lt;br /&gt;
Starting with version 2.96, the Build ID can serve as the software version identifier. The specific request used as the software version identifier can be configured individually for each vehicle.&lt;br /&gt;
&lt;br /&gt;
== Diagnostic tester detection ==&lt;br /&gt;
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use &#039;diagnostic tester detection&#039; in the [[I/O configurations#The Miscellaneous Section|IO tab]] when editing the configuration.&lt;br /&gt;
&lt;br /&gt;
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==&lt;br /&gt;
When viewed in the tasks panel it is now possible to add, edit, or remove ECU SW from validation on [[Creating a Task#M-Log|M-Log]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.&lt;br /&gt;
&lt;br /&gt;
== Support for configurable PIN codes in sequence files for IDC and Signal Reader ==&lt;br /&gt;
If PIC codes have been configured for one or more ECUs in a vehicle connected to a WCU, the PIN codes can be used in diagnostic sequence files in IDC and Signal Reader (DRECs) by referring to the using the naming convention &amp;quot;PIN_&amp;lt;ecuname&amp;gt;_&amp;lt;area&amp;gt;&amp;quot;. The name should be prefixed by a dollar sign to indicate that it is a variable name. For example, the PIN code for area 17 in the ECM ECU can be referenced in a sequence file by $PIN_ECM_17. Note that the area code should be hexadecimal.&lt;br /&gt;
&lt;br /&gt;
== New trigger expression operator in Signal Reader ==&lt;br /&gt;
Signal Reader has a new trigger expression operator TIME_SINCE_UPDATE, which returs the time in seconds since a specified signal was updated. &lt;br /&gt;
&lt;br /&gt;
== New expression for UD signals in Signal Reader ==&lt;br /&gt;
IF-THEN-ELSE expressions are now supported in User Defined signals in Signal Reader.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.96&amp;diff=4099</id>
		<title>New features in v2.96</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.96&amp;diff=4099"/>
		<updated>2025-11-11T08:00:18Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.&lt;br /&gt;
&lt;br /&gt;
== DLT Daemon mode and DLT UDS in parallel ==&lt;br /&gt;
The portal now supports creating DLT tasks with daemon mode and UDS service 38 enabled at the same time. This requires WCU software version 2.96.0 or later for the selected WCUs. See [[Creating a Task#Diagnostic Log and Trace (DLT)|Creating a Task#Diagnostic Log and Trace (DLT).]]&lt;br /&gt;
&lt;br /&gt;
== DLT Daemon address via vehicle announcement ==&lt;br /&gt;
For WCUs configured for software version 2.96.0 it is possible to get the daemon address via vehicle announcement instead of specifying a daemon address when the task is created. See [[Creating a Task#Diagnostic Log and Trace (DLT)|Creating a Task#Diagnostic Log and Trace (DLT).]]&lt;br /&gt;
&lt;br /&gt;
== Set, View, and Apply Default WCU Configurations ==&lt;br /&gt;
Starting from version 2.96, users can now set, view, and apply default WCU configurations. Admin permissions are required to access these new functions. Read more about it [[Default WCU Configuration|here]].&lt;br /&gt;
&lt;br /&gt;
== Users can now shelve a WCU directly from the Vehicles panel ==&lt;br /&gt;
Users with WCU shelving permissions can now shelve a WCU directly in the Vehicles panel. Read more about it [[Shelve and Unshelve a WCU|here]].&lt;br /&gt;
&lt;br /&gt;
== VINReader option to not request VIN if known ==&lt;br /&gt;
A new option is available to silence VINReader on startup if the VIN is already known. When in play, VINReader will stay silent, i.e. not request any VIN, if VIN is already known. However, if VIN is unknown, VINReader will send a request for VIN.&lt;br /&gt;
&lt;br /&gt;
== Support for diagnostic Build ID request ==&lt;br /&gt;
Starting with version 2.96, the Build ID can serve as the software version identifier. The specific request used as the software version identifier can be configured individually for each vehicle.&lt;br /&gt;
&lt;br /&gt;
== Diagnostic tester detection ==&lt;br /&gt;
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use &#039;diagnostic tester detection&#039; in the [[I/O configurations#The Miscellaneous Section|IO tab]] when editing the configuration.&lt;br /&gt;
&lt;br /&gt;
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==&lt;br /&gt;
When viewed in the tasks panel it is now possible to add, edit, or remove ECU SW from validation on [[Creating a Task#M-Log|M-Log]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.&lt;br /&gt;
&lt;br /&gt;
== Support for configurable PIN codes in sequence files for IDC and Signal Reader ==&lt;br /&gt;
If PIC codes have been configured for one or more ECUs in a vehicle connected to a WCU, the PIN codes can be used in diagnostic sequence files in IDC and Signal Reader (DRECs) by referring to the using the naming convention &amp;quot;PIN_&amp;lt;ecuname&amp;gt;_&amp;lt;area&amp;gt;&amp;quot;. The name should be prefixed by a dollar sign to indicate that it is a variable name. For example, the PIN code for area 17 in the ECM ECU can be referenced in a sequence file by $PIN_ECM_17. Note that the area code should be hexadecimal.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4098</id>
		<title>Signal Reader Trigger Expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=4098"/>
		<updated>2025-11-10T07:32:18Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE&lt;br /&gt;
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP&lt;br /&gt;
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN&lt;br /&gt;
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_BY&lt;br /&gt;
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP_BY&lt;br /&gt;
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN_BY&lt;br /&gt;
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_FROM_TO&lt;br /&gt;
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)&lt;br /&gt;
|-&lt;br /&gt;
!TIMER&lt;br /&gt;
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)&lt;br /&gt;
|-&lt;br /&gt;
!EXPR_TIMER&lt;br /&gt;
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!EVERY&lt;br /&gt;
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)&lt;br /&gt;
|-&lt;br /&gt;
!MOVAV&lt;br /&gt;
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|-&lt;br /&gt;
!NO_SIGNAL&lt;br /&gt;
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL(&#039;Signal&#039;, &#039;Numeric Value&#039;)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_SINCE_UPDATE&lt;br /&gt;
|Gives the time in seconds since the specified signal was last updated. Syntax: TIME_SINCE_UPDATE(&#039;Signal&#039;)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Main_Page&amp;diff=3987</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Main_Page&amp;diff=3987"/>
		<updated>2025-08-14T07:46:13Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Welcome to the WICE Wiki!&#039;&#039;&#039;&amp;lt;br&amp;gt;Here you can find information about the WICE System and how-to guides of all the features in the WICE Portal. &lt;br /&gt;
&lt;br /&gt;
The WICE system is a powerful and flexible data collection and fleet management system developed by Alkit Communications AB. The WICE Portal is the user interface of the WICE system. &lt;br /&gt;
&lt;br /&gt;
Feel free to suggest improvements and add pages if you feel that some information is missing.&lt;br /&gt;
&lt;br /&gt;
To see the addtions/changes of the previous version of the WICE portal, see [[New features in v2.94|New features in v2.94.]] (Also available from the sidebar to the left.)&lt;br /&gt;
&lt;br /&gt;
For full release history see [[https://wice-sysdoc.alkit.se/index.php/Release_notes WICE Release history]].&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Main_Page&amp;diff=3986</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Main_Page&amp;diff=3986"/>
		<updated>2025-08-14T07:42:58Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;&#039;Welcome to the WICE Wiki!&#039;&#039;&#039;&amp;lt;br&amp;gt;Here you can find information about the WICE System and how-to guides of all the features in the WICE Portal. &lt;br /&gt;
&lt;br /&gt;
Feel free to suggest improvements and add pages if you feel that some information is missing.&lt;br /&gt;
&lt;br /&gt;
To see the addtions/changes of the previous version of the WICE portal, see [[New features in v2.94|New features in v2.94.]] (Also available from the sidebar to the left.)&lt;br /&gt;
&lt;br /&gt;
For full release history see [[https://wice-sysdoc.alkit.se/index.php/Release_notes WICE Release history]].&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3976</id>
		<title>New features in v2.94</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3976"/>
		<updated>2025-06-16T07:19:44Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Support for admins to download description files. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for labels in vehicle templates ==&lt;br /&gt;
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].&lt;br /&gt;
&lt;br /&gt;
== Extend WCU history to account for more changes ==&lt;br /&gt;
Two new columns have been added to the WCU history: &#039;&#039;&#039;&amp;quot;Type of Change&amp;quot;&#039;&#039;&#039; and &#039;&#039;&#039;&amp;quot;State&amp;quot;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Type of Change&#039;&#039;&#039; indicates whether the update involved a configuration change, a tools change, or a label change.&lt;br /&gt;
* &#039;&#039;&#039;State&#039;&#039;&#039; reflects the WCU’s status at the time of the change, such as &amp;quot;In Operation&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].&lt;br /&gt;
&lt;br /&gt;
== Configurable tester address for signal reader, IDC, SoH and vinreader ==&lt;br /&gt;
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called &#039;Tester Address.&#039; In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]&lt;br /&gt;
&lt;br /&gt;
== Fetch PINs from PIE ==&lt;br /&gt;
[[File:Fetch PINs button.png|thumb|Button to fetch PINs from PIE]]&lt;br /&gt;
As of version 2.94.0 for portals with Vehicle Communication Forwarder (VCF) enabled, it will now be possible to get PINs from PIE for the WCUs in a group via &#039;&#039;Administration&#039;&#039;-&amp;gt;&#039;&#039;Resource groups&#039;&#039;. This will save any found PINs that can then be applied to the VCF&#039;s configuration for each WCU in the group. Read more about configuring VCF [[Vehicle Communication Forwarder|here]].&lt;br /&gt;
&lt;br /&gt;
== New column for WCU state in Vehicles Tab ==&lt;br /&gt;
A new column has been introduced to the Vehicles tab that will show the current state of the WCU.&lt;br /&gt;
&lt;br /&gt;
== Support for SOVD IP Address in the WCU configuration ==&lt;br /&gt;
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the &#039;SOVD IP Address&#039; field located under the Connection tab in the WCU configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function. &lt;br /&gt;
&lt;br /&gt;
== Support to update a subset of WCU configuration variables ==&lt;br /&gt;
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]&lt;br /&gt;
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new &#039;&#039;&#039;&amp;quot;Show Changed Settings&amp;quot;&#039;&#039;&#039; button allows you to easily track any modifications you&#039;ve made. Additionally, a new dropdown menu labeled &#039;&#039;&#039;&amp;quot;Settings from WCU&amp;quot;&#039;&#039;&#039; lets you select which WCU’s configuration you want to edit from. More importantly, only the configuration settings changed will be applied to the WCUs, all other configuration settings will be untouched.&lt;br /&gt;
&lt;br /&gt;
== Support for new platform Kvaser Edge ==&lt;br /&gt;
There is support for a new WCU platform called Kvaser Edge.&lt;br /&gt;
&lt;br /&gt;
== Support for admins to download description files ==&lt;br /&gt;
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]&lt;br /&gt;
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in the Administration-&amp;gt;Vehicle Profiles panel.&lt;br /&gt;
&lt;br /&gt;
== New alarm when a shelved WCU tries to connect with a vehicle ==&lt;br /&gt;
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is &#039;wcu::state::shelved::connect&#039;.&lt;br /&gt;
&lt;br /&gt;
== Support for show signal info for all signals in assignment editor ==&lt;br /&gt;
&lt;br /&gt;
== Frame names in add signals for assignment editor ==&lt;br /&gt;
You can now view the frame name for both CAN and LIN signals directly within the &amp;quot;Add Signal&amp;quot; dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.&lt;br /&gt;
&lt;br /&gt;
== Improved assignment editor permission ==&lt;br /&gt;
We&#039;ve upgraded the assignment permission settings to give more control.&lt;br /&gt;
&lt;br /&gt;
Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved handling of copy assignment ==&lt;br /&gt;
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.&lt;br /&gt;
&lt;br /&gt;
The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.&lt;br /&gt;
&lt;br /&gt;
== Support to see when a label was associated with a resource ==&lt;br /&gt;
[[File:New label viewer.png|thumb|101x101px|New label viewer]]&lt;br /&gt;
There is now support to see at what time a specific label was associated with a resource.&lt;br /&gt;
&lt;br /&gt;
== Support to search for empty values in label columns ==&lt;br /&gt;
You can now search for the absence of values in your label columns in various places.&lt;br /&gt;
&lt;br /&gt;
== Cybersecurity settings ==&lt;br /&gt;
For the WCU a bunch of cybersecurity settings are available.&lt;br /&gt;
&lt;br /&gt;
* Disable USB ethernet interfaces&lt;br /&gt;
* Lock Signal Reader&#039;s Signal Broker communication to localhost&lt;br /&gt;
* Disable the SSH daemon&lt;br /&gt;
* Root password checks to prevent too weak passwords&lt;br /&gt;
* Software firewall on the WCU&lt;br /&gt;
&lt;br /&gt;
== Instant downloads of multiple files ==&lt;br /&gt;
From version 2.94 the previous background zipping of files described in [[Downloading Files]] is no longer needed. Instead the downloading starts immediately when clicking the &amp;quot;Get all files&amp;quot; button in [[Tasks Tab]] or the &amp;quot;Download&amp;quot; button in the [[Search Tab]].&lt;br /&gt;
== Improved CAN frame logging in Signal Reader ==&lt;br /&gt;
The CAN frame logging has been improved to support CANFD frame logging and to support finalization of MF4 frame logs in recovery mode.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3975</id>
		<title>New features in v2.94</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3975"/>
		<updated>2025-06-16T07:19:02Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for labels in vehicle templates ==&lt;br /&gt;
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].&lt;br /&gt;
&lt;br /&gt;
== Extend WCU history to account for more changes ==&lt;br /&gt;
Two new columns have been added to the WCU history: &#039;&#039;&#039;&amp;quot;Type of Change&amp;quot;&#039;&#039;&#039; and &#039;&#039;&#039;&amp;quot;State&amp;quot;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Type of Change&#039;&#039;&#039; indicates whether the update involved a configuration change, a tools change, or a label change.&lt;br /&gt;
* &#039;&#039;&#039;State&#039;&#039;&#039; reflects the WCU’s status at the time of the change, such as &amp;quot;In Operation&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].&lt;br /&gt;
&lt;br /&gt;
== Configurable tester address for signal reader, IDC, SoH and vinreader ==&lt;br /&gt;
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called &#039;Tester Address.&#039; In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]&lt;br /&gt;
&lt;br /&gt;
== Fetch PINs from PIE ==&lt;br /&gt;
[[File:Fetch PINs button.png|thumb|Button to fetch PINs from PIE]]&lt;br /&gt;
As of version 2.94.0 for portals with Vehicle Communication Forwarder (VCF) enabled, it will now be possible to get PINs from PIE for the WCUs in a group via &#039;&#039;Administration&#039;&#039;-&amp;gt;&#039;&#039;Resource groups&#039;&#039;. This will save any found PINs that can then be applied to the VCF&#039;s configuration for each WCU in the group. Read more about configuring VCF [[Vehicle Communication Forwarder|here]].&lt;br /&gt;
&lt;br /&gt;
== New column for WCU state in Vehicles Tab ==&lt;br /&gt;
A new column has been introduced to the Vehicles tab that will show the current state of the WCU.&lt;br /&gt;
&lt;br /&gt;
== Support for SOVD IP Address in the WCU configuration ==&lt;br /&gt;
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the &#039;SOVD IP Address&#039; field located under the Connection tab in the WCU configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function. &lt;br /&gt;
&lt;br /&gt;
== Support to update a subset of WCU configuration variables ==&lt;br /&gt;
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]&lt;br /&gt;
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new &#039;&#039;&#039;&amp;quot;Show Changed Settings&amp;quot;&#039;&#039;&#039; button allows you to easily track any modifications you&#039;ve made. Additionally, a new dropdown menu labeled &#039;&#039;&#039;&amp;quot;Settings from WCU&amp;quot;&#039;&#039;&#039; lets you select which WCU’s configuration you want to edit from. More importantly, only the configuration settings changed will be applied to the WCUs, all other configuration settings will be untouched.&lt;br /&gt;
&lt;br /&gt;
== Support for new platform Kvaser Edge ==&lt;br /&gt;
There is support for a new WCU platform called Kvaser Edge.&lt;br /&gt;
&lt;br /&gt;
== Support for admins to download description files. ==&lt;br /&gt;
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]&lt;br /&gt;
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in the Administration-&amp;gt;Vehicle Profiles panel.&lt;br /&gt;
&lt;br /&gt;
== New alarm when a shelved WCU tries to connect with a vehicle ==&lt;br /&gt;
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is &#039;wcu::state::shelved::connect&#039;.&lt;br /&gt;
&lt;br /&gt;
== Support for show signal info for all signals in assignment editor ==&lt;br /&gt;
&lt;br /&gt;
== Frame names in add signals for assignment editor ==&lt;br /&gt;
You can now view the frame name for both CAN and LIN signals directly within the &amp;quot;Add Signal&amp;quot; dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.&lt;br /&gt;
&lt;br /&gt;
== Improved assignment editor permission ==&lt;br /&gt;
We&#039;ve upgraded the assignment permission settings to give more control.&lt;br /&gt;
&lt;br /&gt;
Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved handling of copy assignment ==&lt;br /&gt;
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.&lt;br /&gt;
&lt;br /&gt;
The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.&lt;br /&gt;
&lt;br /&gt;
== Support to see when a label was associated with a resource ==&lt;br /&gt;
[[File:New label viewer.png|thumb|101x101px|New label viewer]]&lt;br /&gt;
There is now support to see at what time a specific label was associated with a resource.&lt;br /&gt;
&lt;br /&gt;
== Support to search for empty values in label columns ==&lt;br /&gt;
You can now search for the absence of values in your label columns in various places.&lt;br /&gt;
&lt;br /&gt;
== Cybersecurity settings ==&lt;br /&gt;
For the WCU a bunch of cybersecurity settings are available.&lt;br /&gt;
&lt;br /&gt;
* Disable USB ethernet interfaces&lt;br /&gt;
* Lock Signal Reader&#039;s Signal Broker communication to localhost&lt;br /&gt;
* Disable the SSH daemon&lt;br /&gt;
* Root password checks to prevent too weak passwords&lt;br /&gt;
* Software firewall on the WCU&lt;br /&gt;
&lt;br /&gt;
== Instant downloads of multiple files ==&lt;br /&gt;
From version 2.94 the previous background zipping of files described in [[Downloading Files]] is no longer needed. Instead the downloading starts immediately when clicking the &amp;quot;Get all files&amp;quot; button in [[Tasks Tab]] or the &amp;quot;Download&amp;quot; button in the [[Search Tab]].&lt;br /&gt;
== Improved CAN frame logging in Signal Reader ==&lt;br /&gt;
The CAN frame logging has been improved to support CANFD frame logging and to support finalization of MF4 frame logs in recovery mode.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3974</id>
		<title>New features in v2.94</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3974"/>
		<updated>2025-06-16T07:15:18Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Cybersecurity settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for labels in vehicle templates ==&lt;br /&gt;
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].&lt;br /&gt;
&lt;br /&gt;
== Extend WCU history to account for more changes ==&lt;br /&gt;
Two new columns have been added to the WCU history: &#039;&#039;&#039;&amp;quot;Type of Change&amp;quot;&#039;&#039;&#039; and &#039;&#039;&#039;&amp;quot;State&amp;quot;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Type of Change&#039;&#039;&#039; indicates whether the update involved a configuration change, a tools change, or a label change.&lt;br /&gt;
* &#039;&#039;&#039;State&#039;&#039;&#039; reflects the WCU’s status at the time of the change, such as &amp;quot;In Operation&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].&lt;br /&gt;
&lt;br /&gt;
== Configurable tester address for signal reader, IDC, SoH and vinreader ==&lt;br /&gt;
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called &#039;Tester Address.&#039; In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]&lt;br /&gt;
&lt;br /&gt;
== Fetch PINs from PIE ==&lt;br /&gt;
[[File:Fetch PINs button.png|thumb|Button to fetch PINs from PIE]]&lt;br /&gt;
As of version 2.94.0 for portals with Vehicle Communication Forwarder (VCF) enabled, it will now be possible to get PINs from PIE for the WCUs in a group via &#039;&#039;Administration&#039;&#039;-&amp;gt;&#039;&#039;Resource groups&#039;&#039;. This will save any found PINs that can then be applied to the VCF&#039;s configuration for each WCU in the group. Read more about configuring VCF [[Vehicle Communication Forwarder|here]].&lt;br /&gt;
&lt;br /&gt;
== New column for WCU state in Vehicles Tab ==&lt;br /&gt;
A new column has been introduced to the Vehicles tab that will show the current state of the WCU.&lt;br /&gt;
&lt;br /&gt;
== Support for SOVD IP Address in the WCU configuration ==&lt;br /&gt;
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the &#039;SOVD IP Address&#039; field located under the Connection tab in the WCU configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function. &lt;br /&gt;
&lt;br /&gt;
== Support to update a subset of WCU configuration variables ==&lt;br /&gt;
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]&lt;br /&gt;
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new &#039;&#039;&#039;&amp;quot;Show Changed Settings&amp;quot;&#039;&#039;&#039; button allows you to easily track any modifications you&#039;ve made. Additionally, a new dropdown menu labeled &#039;&#039;&#039;&amp;quot;Settings from WCU&amp;quot;&#039;&#039;&#039; lets you select which WCU’s configuration you want to edit from. More importantly, only the configuration settings changed will be applied to the WCUs, all other configuration settings will be untouched.&lt;br /&gt;
&lt;br /&gt;
== Support for new platform Kvaser Edge ==&lt;br /&gt;
There is support for a new WCU platform called Kvaser Edge.&lt;br /&gt;
&lt;br /&gt;
== Support for admins to download description files. ==&lt;br /&gt;
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]&lt;br /&gt;
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in the Administration-&amp;gt;Vehicle Profiles panel.&lt;br /&gt;
&lt;br /&gt;
== New alarm when a shelved WCU tries to connect with a vehicle ==&lt;br /&gt;
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is &#039;wcu::state::shelved::connect&#039;.&lt;br /&gt;
&lt;br /&gt;
== Support for show signal info for all signals in assignment editor ==&lt;br /&gt;
&lt;br /&gt;
== Frame names in add signals for assignment editor ==&lt;br /&gt;
You can now view the frame name for both CAN and LIN signals directly within the &amp;quot;Add Signal&amp;quot; dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.&lt;br /&gt;
&lt;br /&gt;
== Improved assignment editor permission ==&lt;br /&gt;
We&#039;ve upgraded the assignment permission settings to give more control.&lt;br /&gt;
&lt;br /&gt;
Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved handling of copy assignment ==&lt;br /&gt;
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.&lt;br /&gt;
&lt;br /&gt;
The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.&lt;br /&gt;
&lt;br /&gt;
== Support to see when a label was associated with a resource ==&lt;br /&gt;
[[File:New label viewer.png|thumb|101x101px|New label viewer]]&lt;br /&gt;
There is now support to see at what time a specific label was associated with a resource.&lt;br /&gt;
&lt;br /&gt;
== Support to search for empty values in label columns ==&lt;br /&gt;
You can now search for the absence of values in your label columns in various places.&lt;br /&gt;
&lt;br /&gt;
== Cybersecurity settings ==&lt;br /&gt;
For the WCU a bunch of cybersecurity settings are available.&lt;br /&gt;
&lt;br /&gt;
* Disable USB ethernet interfaces&lt;br /&gt;
* Lock Signal Reader&#039;s Signal Broker communication to localhost&lt;br /&gt;
* Disable the SSH daemon&lt;br /&gt;
* Root password checks to prevent too weak passwords&lt;br /&gt;
* Software firewall on the WCU&lt;br /&gt;
&lt;br /&gt;
== Instant downloads of multiple files ==&lt;br /&gt;
From version 2.94 the previous background zipping of files described in [[Downloading Files]] is no longer needed. Instead the downloading starts immediately when clicking the &amp;quot;Get all files&amp;quot; button in [[Tasks Tab]] or the &amp;quot;Download&amp;quot; button in the [[Search Tab]].&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3973</id>
		<title>New features in v2.94</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3973"/>
		<updated>2025-06-16T07:11:07Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Cyber security settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for labels in vehicle templates ==&lt;br /&gt;
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].&lt;br /&gt;
&lt;br /&gt;
== Extend WCU history to account for more changes ==&lt;br /&gt;
Two new columns have been added to the WCU history: &#039;&#039;&#039;&amp;quot;Type of Change&amp;quot;&#039;&#039;&#039; and &#039;&#039;&#039;&amp;quot;State&amp;quot;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Type of Change&#039;&#039;&#039; indicates whether the update involved a configuration change, a tools change, or a label change.&lt;br /&gt;
* &#039;&#039;&#039;State&#039;&#039;&#039; reflects the WCU’s status at the time of the change, such as &amp;quot;In Operation&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].&lt;br /&gt;
&lt;br /&gt;
== Configurable tester address for signal reader, IDC, SoH and vinreader ==&lt;br /&gt;
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called &#039;Tester Address.&#039; In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]&lt;br /&gt;
&lt;br /&gt;
== Fetch PINs from PIE ==&lt;br /&gt;
[[File:Fetch PINs button.png|thumb|Button to fetch PINs from PIE]]&lt;br /&gt;
As of version 2.94.0 for portals with Vehicle Communication Forwarder (VCF) enabled, it will now be possible to get PINs from PIE for the WCUs in a group via &#039;&#039;Administration&#039;&#039;-&amp;gt;&#039;&#039;Resource groups&#039;&#039;. This will save any found PINs that can then be applied to the VCF&#039;s configuration for each WCU in the group. Read more about configuring VCF [[Vehicle Communication Forwarder|here]].&lt;br /&gt;
&lt;br /&gt;
== New column for WCU state in Vehicles Tab ==&lt;br /&gt;
A new column has been introduced to the Vehicles tab that will show the current state of the WCU.&lt;br /&gt;
&lt;br /&gt;
== Support for SOVD IP Address in the WCU configuration ==&lt;br /&gt;
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the &#039;SOVD IP Address&#039; field located under the Connection tab in the WCU configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function. &lt;br /&gt;
&lt;br /&gt;
== Support to update a subset of WCU configuration variables ==&lt;br /&gt;
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]&lt;br /&gt;
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new &#039;&#039;&#039;&amp;quot;Show Changed Settings&amp;quot;&#039;&#039;&#039; button allows you to easily track any modifications you&#039;ve made. Additionally, a new dropdown menu labeled &#039;&#039;&#039;&amp;quot;Settings from WCU&amp;quot;&#039;&#039;&#039; lets you select which WCU’s configuration you want to edit from. More importantly, only the configuration settings changed will be applied to the WCUs, all other configuration settings will be untouched.&lt;br /&gt;
&lt;br /&gt;
== Support for new platform Kvaser Edge ==&lt;br /&gt;
There is support for a new WCU platform called Kvaser Edge.&lt;br /&gt;
&lt;br /&gt;
== Support for admins to download description files. ==&lt;br /&gt;
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]&lt;br /&gt;
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in the Administration-&amp;gt;Vehicle Profiles panel.&lt;br /&gt;
&lt;br /&gt;
== New alarm when a shelved WCU tries to connect with a vehicle ==&lt;br /&gt;
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is &#039;wcu::state::shelved::connect&#039;.&lt;br /&gt;
&lt;br /&gt;
== Support for show signal info for all signals in assignment editor ==&lt;br /&gt;
&lt;br /&gt;
== Frame names in add signals for assignment editor ==&lt;br /&gt;
You can now view the frame name for both CAN and LIN signals directly within the &amp;quot;Add Signal&amp;quot; dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.&lt;br /&gt;
&lt;br /&gt;
== Improved assignment editor permission ==&lt;br /&gt;
We&#039;ve upgraded the assignment permission settings to give more control.&lt;br /&gt;
&lt;br /&gt;
Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved handling of copy assignment ==&lt;br /&gt;
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.&lt;br /&gt;
&lt;br /&gt;
The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.&lt;br /&gt;
&lt;br /&gt;
== Support to see when a label was associated with a resource ==&lt;br /&gt;
[[File:New label viewer.png|thumb|101x101px|New label viewer]]&lt;br /&gt;
There is now support to see at what time a specific label was associated with a resource.&lt;br /&gt;
&lt;br /&gt;
== Support to search for empty values in label columns ==&lt;br /&gt;
You can now search for the absence of values in your label columns in various places.&lt;br /&gt;
&lt;br /&gt;
== Cybersecurity settings ==&lt;br /&gt;
For the WCU a bunch of cybersecurity settings are available.&lt;br /&gt;
&lt;br /&gt;
* Disable USB ethernet interfaces&lt;br /&gt;
* Lock signal reader pub/sub communication to localhost&lt;br /&gt;
* Disable the SSH daemon&lt;br /&gt;
* Root password checks to prevent too weak passwords&lt;br /&gt;
&lt;br /&gt;
== Instant downloads of multiple files ==&lt;br /&gt;
From version 2.94 the previous background zipping of files described in [[Downloading Files]] is no longer needed. Instead the downloading starts immediately when clicking the &amp;quot;Get all files&amp;quot; button in [[Tasks Tab]] or the &amp;quot;Download&amp;quot; button in the [[Search Tab]].&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3972</id>
		<title>New features in v2.94</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.94&amp;diff=3972"/>
		<updated>2025-06-16T07:10:44Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Support for new platform Kvaser Edge */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for labels in vehicle templates ==&lt;br /&gt;
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].&lt;br /&gt;
&lt;br /&gt;
== Extend WCU history to account for more changes ==&lt;br /&gt;
Two new columns have been added to the WCU history: &#039;&#039;&#039;&amp;quot;Type of Change&amp;quot;&#039;&#039;&#039; and &#039;&#039;&#039;&amp;quot;State&amp;quot;&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Type of Change&#039;&#039;&#039; indicates whether the update involved a configuration change, a tools change, or a label change.&lt;br /&gt;
* &#039;&#039;&#039;State&#039;&#039;&#039; reflects the WCU’s status at the time of the change, such as &amp;quot;In Operation&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].&lt;br /&gt;
&lt;br /&gt;
== Configurable tester address for signal reader, IDC, SoH and vinreader ==&lt;br /&gt;
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called &#039;Tester Address.&#039; In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]&lt;br /&gt;
&lt;br /&gt;
== Fetch PINs from PIE ==&lt;br /&gt;
[[File:Fetch PINs button.png|thumb|Button to fetch PINs from PIE]]&lt;br /&gt;
As of version 2.94.0 for portals with Vehicle Communication Forwarder (VCF) enabled, it will now be possible to get PINs from PIE for the WCUs in a group via &#039;&#039;Administration&#039;&#039;-&amp;gt;&#039;&#039;Resource groups&#039;&#039;. This will save any found PINs that can then be applied to the VCF&#039;s configuration for each WCU in the group. Read more about configuring VCF [[Vehicle Communication Forwarder|here]].&lt;br /&gt;
&lt;br /&gt;
== New column for WCU state in Vehicles Tab ==&lt;br /&gt;
A new column has been introduced to the Vehicles tab that will show the current state of the WCU.&lt;br /&gt;
&lt;br /&gt;
== Support for SOVD IP Address in the WCU configuration ==&lt;br /&gt;
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the &#039;SOVD IP Address&#039; field located under the Connection tab in the WCU configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function. &lt;br /&gt;
&lt;br /&gt;
== Support to update a subset of WCU configuration variables ==&lt;br /&gt;
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]&lt;br /&gt;
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new &#039;&#039;&#039;&amp;quot;Show Changed Settings&amp;quot;&#039;&#039;&#039; button allows you to easily track any modifications you&#039;ve made. Additionally, a new dropdown menu labeled &#039;&#039;&#039;&amp;quot;Settings from WCU&amp;quot;&#039;&#039;&#039; lets you select which WCU’s configuration you want to edit from. More importantly, only the configuration settings changed will be applied to the WCUs, all other configuration settings will be untouched.&lt;br /&gt;
&lt;br /&gt;
== Support for new platform Kvaser Edge ==&lt;br /&gt;
There is support for a new WCU platform called Kvaser Edge.&lt;br /&gt;
&lt;br /&gt;
== Support for admins to download description files. ==&lt;br /&gt;
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]&lt;br /&gt;
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in the Administration-&amp;gt;Vehicle Profiles panel.&lt;br /&gt;
&lt;br /&gt;
== New alarm when a shelved WCU tries to connect with a vehicle ==&lt;br /&gt;
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is &#039;wcu::state::shelved::connect&#039;.&lt;br /&gt;
&lt;br /&gt;
== Support for show signal info for all signals in assignment editor ==&lt;br /&gt;
&lt;br /&gt;
== Frame names in add signals for assignment editor ==&lt;br /&gt;
You can now view the frame name for both CAN and LIN signals directly within the &amp;quot;Add Signal&amp;quot; dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.&lt;br /&gt;
&lt;br /&gt;
== Improved assignment editor permission ==&lt;br /&gt;
We&#039;ve upgraded the assignment permission settings to give more control.&lt;br /&gt;
&lt;br /&gt;
Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved handling of copy assignment ==&lt;br /&gt;
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.&lt;br /&gt;
&lt;br /&gt;
The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.&lt;br /&gt;
&lt;br /&gt;
== Support to see when a label was associated with a resource ==&lt;br /&gt;
[[File:New label viewer.png|thumb|101x101px|New label viewer]]&lt;br /&gt;
There is now support to see at what time a specific label was associated with a resource.&lt;br /&gt;
&lt;br /&gt;
== Support to search for empty values in label columns ==&lt;br /&gt;
You can now search for the absence of values in your label columns in various places.&lt;br /&gt;
&lt;br /&gt;
== Cyber security settings ==&lt;br /&gt;
For the WCU a bunch of cyber security settings are available.&lt;br /&gt;
&lt;br /&gt;
* Disable USB ethernet interfaces&lt;br /&gt;
* Lock signal reader pub/sub communication to localhost&lt;br /&gt;
* Disable the SSH daemon&lt;br /&gt;
* Root password checks to prevent too weak passwords&lt;br /&gt;
&lt;br /&gt;
== Instant downloads of multiple files ==&lt;br /&gt;
From version 2.94 the previous background zipping of files described in [[Downloading Files]] is no longer needed. Instead the downloading starts immediately when clicking the &amp;quot;Get all files&amp;quot; button in [[Tasks Tab]] or the &amp;quot;Download&amp;quot; button in the [[Search Tab]].&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3883</id>
		<title>WCU platform</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3883"/>
		<updated>2025-04-25T07:56:23Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* WCU Hardware Platform */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Wireless Communication Unit (WCU) is the in-vehicle unit running the WICE WCU software and communicating with the vehicle and the WICE back-end.&lt;br /&gt;
&lt;br /&gt;
WCU:s are identified by a unique text string, which by convention is the MAC address of (one of) the ethernet interfaces in the unit. The WCU id is configured on each WCU (automatically from the MAC address) and is a search parameter available in the WICE Portal web-GUI.&lt;br /&gt;
&lt;br /&gt;
=== WCU Hardware Platform ===&lt;br /&gt;
The following hardware platforms are supported for the WICE WCU:&lt;br /&gt;
&lt;br /&gt;
* Host Mobility MX-4 (T20, T30, T30FR and V61)&lt;br /&gt;
* SETEK HMX &lt;br /&gt;
* Raspberry Pi&lt;br /&gt;
* Nvidia Jetson Xavier&lt;br /&gt;
&lt;br /&gt;
Depending on the specific hardware platform, the WCU supports a number of communication interfaces, such as CAN, LIN, FlexRay and Ethernet and that be configured in different ways using the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
The WCU has the following communication interfaces (some of which are optional):&lt;br /&gt;
&lt;br /&gt;
* a point-to-point (ppp) interface using a 2G/3G/4G mobile data modem&lt;br /&gt;
* optionally, a WiFi wireless LAN interface&lt;br /&gt;
* one to four wired ethernet interfaces.&lt;br /&gt;
* two to six Controller Area Network (CAN) interfaces&lt;br /&gt;
* optionally a FlexRay interface&lt;br /&gt;
* optionally, one or more LIN interfaces&lt;br /&gt;
* one to two USB interfaces.&lt;br /&gt;
&lt;br /&gt;
The unit has the following storage mechanisms:&lt;br /&gt;
&lt;br /&gt;
* internal flash memory for persistent storage&lt;br /&gt;
* removable SD card for temporary storage&lt;br /&gt;
&lt;br /&gt;
The unit has the following power modes:&lt;br /&gt;
&lt;br /&gt;
* running (full functionality available)&lt;br /&gt;
* sleep (suspended state)&lt;br /&gt;
* deep sleep (low-power suspended state)&lt;br /&gt;
&lt;br /&gt;
The WCU platform can also support some limited user-interaction through light-emitting diodes (LED) on the side of the unit. A description of the LEDs is available  [[WCU LEDs|here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Firmware ===&lt;br /&gt;
The WCU firmware is the operating system, device drivers and basic packages required to run the system. The WCU units are delivered with the firmware installed. It can be remotely upgraded from the WICE Portal in a similar way as the WCU Software (see below).&lt;br /&gt;
&lt;br /&gt;
=== WCU Software  ===&lt;br /&gt;
The WCU software is delivered as a self-extracting application installation package, which can be run on the WCU:s manually from a command prompt, using a suitably prepared USB stick, or updated remotely using the WICE Portal mechanism for remote software upgrades.&lt;br /&gt;
&lt;br /&gt;
The WICE solution for remote update of the WCU software works as follows: The Alkit staff member responsible for the WCU software deployment publishes installation packages for supported versions of the WCU software at the WICE Portal, in the WICE back-end server infrastructure. WICE administrators can then select which version of the available WCU software versions should be run on each of the WCUs that are registered in the system (see [[The Portal Administrator View#Edit the WCU Configuration|Edit WCU Configuration]]). This is done by choosing a particular version in a drop-down menu in the WICE Portal in the WCU configuration view. Many WCUs can be configured at the same time.&lt;br /&gt;
Then, whenever a WCU connects to the back-end, a check is made to see whether a different WCU software version (higher or lower version) than the currently installed version for the WCU in question is configured. If so, the installation package is downloaded to the WCU’s solid-state storage over the secure TLS connection that was established when the WCU connected. When the download is finished, the WCU software package will be installed on the WCU. After the installation has finished, the WCU will report back to the WICE back-end infrastructure with the new version of the WCU, so that WICE administrators can keep track of the currently installed software version, as well as the history of software changes.&lt;br /&gt;
A similar process is performed to update the WCU firmware and operating system. When new firmware is installed, the partition where the certificate and configuration files reside is left unaltered.&lt;br /&gt;
&lt;br /&gt;
The WCU software release history is available [[https://wice-sysdoc.alkit.se/index.php/WICE_WCU_Software_Revision_History here]].&lt;br /&gt;
&lt;br /&gt;
==== Extra Bundles ====&lt;br /&gt;
Some WICE software packages, referred to as &#039;extra bundles&#039; are not installed by default. The user needs to select which, if any, extra bundles should be installed on a particular WCU. This is done in the WICE Portal, Edit Configuration. [[Extra bundles|For more information about Extra bundles, click here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Modules ===&lt;br /&gt;
The WCU Modules are the software components of the WCU producing&lt;br /&gt;
measurement data. They are configured through the Configuration Manager, which communicates with the WICE Portal, where the user can access and change the overall WCU configuration and the per-module configurations.&lt;br /&gt;
&lt;br /&gt;
The data capture behavior of the WCU modules is described by a measurement task, downloaded from the WICE Portal by the Task Manager component, which sets up the modules.&lt;br /&gt;
&lt;br /&gt;
The available WCU modules are:  &lt;br /&gt;
* Arcos&lt;br /&gt;
* Area5&lt;br /&gt;
* Audio&lt;br /&gt;
* Blue piraT&lt;br /&gt;
* Canrecorder&lt;br /&gt;
* DLT&lt;br /&gt;
* DoIP&lt;br /&gt;
* ETAS&lt;br /&gt;
* Ethernet capture&lt;br /&gt;
* File fetcher&lt;br /&gt;
* GPS&lt;br /&gt;
* IDC&lt;br /&gt;
* IPEmotion RT&lt;br /&gt;
* LPD&lt;br /&gt;
* M-Log&lt;br /&gt;
* MQTT&lt;br /&gt;
* Rapid Prototyping&lt;br /&gt;
* Signal Reader&lt;br /&gt;
* State-of-Health&lt;br /&gt;
* SWDL&lt;br /&gt;
* Video &lt;br /&gt;
* WCU internals and status&lt;br /&gt;
&lt;br /&gt;
==== Arcos module ====&lt;br /&gt;
The Arcos module makes it possible to use an Arcos data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the Arcos and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== Area5 module ====&lt;br /&gt;
The Area5 module is used to read out ECU memory segments using CCP or XCP. The binary data of the memory segments are uploaded to the back-end where they are translated into parameter sets and signals.  &lt;br /&gt;
&lt;br /&gt;
==== Audio module ====&lt;br /&gt;
The audio module makes it possible to record sound clips from microphones connected to the audio devices of WCUs. Audio can also be streamed in real time from WCUs for live audio monitoring purposes.&lt;br /&gt;
The recording of audio can be triggered by a push button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started or when the trigger condition is fulfilled the audio recording starts, and when the recorder stops, the audio recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Audio sample rate, number of channels (mono or stereo) and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== Blue piraT Module ====&lt;br /&gt;
The Blue piraT module makes it possible to use a Blue piraT logger connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement configuration can be downloaded to the logger and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== CAN Recorder Module ====&lt;br /&gt;
The CAN Recorder Module supports frame logging on the CAN-buses the WCU is connected to. Filters for the ECU identifiers to log can be&lt;br /&gt;
defined in the WICE Portal interface when creating a CAN Recorder measurement task.&lt;br /&gt;
&lt;br /&gt;
==== DLT module ====&lt;br /&gt;
The DLT module supports read-out of Diagnostic Log Trace files. The read-out can be done either using an in-vehicle DLT daemon, or using UDS Service 38 file transfer. See [[DLT Module|DLT module]].&lt;br /&gt;
&lt;br /&gt;
==== DoIP module ====&lt;br /&gt;
The DoIP module makes it possible to establish a tunnel over the Internet to a WCU for synchronous communication using the DoIP protocol.&lt;br /&gt;
In the WCU, the remote DoIP functionality is based on the DoIP daemon &#039;&#039;&#039;doipd&#039;&#039;&#039;, which relays DoIP communication between vehicle and the back-end. &lt;br /&gt;
It also takes care of waking up the vehicle when communication requests are pending. For more information see [[Remote Diagnostics over IP (DoIP)|Remote Diagnostics over IP (DoIP)]].&lt;br /&gt;
&lt;br /&gt;
==== Ethernet Capture Module ====&lt;br /&gt;
The Ethernet Capture module supports logging of ethernet frames on one of the WCU&#039;s ethernet interfaces. Filters can be set (in tcpdump format) for selecting which frames to capture. The result is logged in a pcap file, which is uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== ETAS Module ====&lt;br /&gt;
The ETAS module makes it possible to use an ETAS ES720 measurement system connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement tasks can be downloaded to the ES720 and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== File Fetcher Module ====&lt;br /&gt;
The File Fetcher module supports uploading of files collected from a unit connected to the WCU. &lt;br /&gt;
&lt;br /&gt;
==== GPS Module ====&lt;br /&gt;
The GPS Module reads the position of a WCU at regular intervals and&lt;br /&gt;
reports to the WICE Portal, to support map-based localization of vehicles for the fleet-management service and for the &amp;quot;Plot Route&amp;quot; function of the metrology service.&lt;br /&gt;
&lt;br /&gt;
==== IDC module ====&lt;br /&gt;
The IDC module allows a sequence of diagnostic requests to be sent on the&lt;br /&gt;
in-vehicle network (either CAN or Ethernet), and the responses are collected in a result file. IDC can also read OBD-II PIDs and interpret the responses.&lt;br /&gt;
IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.&lt;br /&gt;
An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].&lt;br /&gt;
&lt;br /&gt;
==== IPEmotion RT ====&lt;br /&gt;
The IPEmotion RT module makes it possible to use an IPEmotion RT data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the logger and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== LPD module ====&lt;br /&gt;
The LPD module supports long term driveline testing using a custom built Android app that connects to the WICE WCU. &lt;br /&gt;
&lt;br /&gt;
==== M-Log module ====&lt;br /&gt;
The M-log module makes it possible to use an M-Log data logger connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the M-Log and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== MQTT module ====&lt;br /&gt;
The MQTT module makes it possible to collect data from another system using an MQTT broker and specifying MQTT topics.&lt;br /&gt;
&lt;br /&gt;
==== Rapid Prototyping module ====&lt;br /&gt;
With the Rapid Prototyping (RP) module, custom software components can be run on the WCU for proof-of-concept testing of new in-vehicle functionality. A Signal Broker API (provided by the Signal Reader module, see below) can be used to easily access in-vehicle signals and parameters. Output data from the RP module is uploaded to the WICE back-end where it is made available in the WICE Portal. The RP module supports both native applications, compiled for the WCU processor architecture, and Node.js applications written in Javascript. The latter is particularly useful for providing in-vehicle GUI functionality.&lt;br /&gt;
&lt;br /&gt;
For more information see [[WICE_RP_How-To]].&lt;br /&gt;
&lt;br /&gt;
==== Signal Reader Module ====&lt;br /&gt;
The Signal Reader module executes a measurement task, monitors and logs time-series signal data and stores the data in an MDF file (Measurement Data&lt;br /&gt;
Format). Signals can be recorded from the vehicle&#039;s internal communication buses (e.g. CAN, LIN, FlexRay). A number of signals internal to the WCU are also available: [[WICE Internal Signals|WICE Internal Signals]]&lt;br /&gt;
&lt;br /&gt;
Signal Reader also supports logging of signals using CCP, XCP and UDS diagnostics. This is sometimes referred to as Active signals.&lt;br /&gt;
&lt;br /&gt;
Triggers are supported, switching between measurement set-ups and starting and stopping recorders. Trigger expression syntax is described [[Signal Reader Trigger Expressions|here]]. Pre- and post-trig recording can be specified, which results in signal data being recorded prior to or subsequent to a trigger condition respectively. Minimum and maximum shot lengths of recorders can also be specified.&lt;br /&gt;
&lt;br /&gt;
==== State of Health Module ====&lt;br /&gt;
The State-of-Health (SoH) module is used to read out a limited data set&lt;br /&gt;
from test vehicles to monitor their operational status. The specific data to be read is configurable from the WICE portal and includes&lt;br /&gt;
position, mileage (odometer), battery voltage, ECU software numbers, Diagnostic Trouble Codes and uptime. The SoH module uses the IDC module to&lt;br /&gt;
service a sequence of diagnostic requests, created by the WICE Portal&lt;br /&gt;
based on which data is requested and the diagnostic database of the vehicle type. Position is accessed from the GPS Module (see below)&lt;br /&gt;
and uptime is accessed from the WCU internal module (see below).&lt;br /&gt;
&lt;br /&gt;
==== SWDL module ====&lt;br /&gt;
The Software Download (SWDL) module makes it possible to download ECU software to connected vehicles for re-programming. The input to the SWDL module is a number of VBF (Versatile Binary Format) files containing the ECU software, and PIN codes for the ECUs to be reprogrammed. Sequence files can also be supplied for pre- and post-programming diagnostics.&lt;br /&gt;
&lt;br /&gt;
==== Video module ====&lt;br /&gt;
The video module makes it possible to record video clips from cameras connected to the WCU. Video can also be streamed in real time from WCUs for live video monitoring purposes.&lt;br /&gt;
The recording of video can be triggered by a push-button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started (i.e. when a trigger condition is fulfilled) the video recording starts, and when the recorder stops, the video recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Video resolution, frame rate and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== WCU internals Module ====&lt;br /&gt;
The WCU internals Module logs useful information about a WCU, including&lt;br /&gt;
uptime, battery voltage (on the WCU power input), and memory usage.&lt;br /&gt;
&lt;br /&gt;
==== WCU Status Module ====&lt;br /&gt;
The WCU status Daemon, statusd,&lt;br /&gt;
monitors the status of the WCU, including all the modules, and&lt;br /&gt;
reports to the WICE Portal. The daemon also provides a common i/o API&lt;br /&gt;
for all modules, including GPS and digital i/o.&lt;br /&gt;
&lt;br /&gt;
=== Power Management ===&lt;br /&gt;
The Power Management settings of the WCU determines how and when the unit is started and shut down. What Power Management mechanisms are available depends on the WCU hardware platform. The following refers to the MX4 platform.&lt;br /&gt;
The MX4 unit can be started and stopped based on the &#039;&#039;ignition&#039;&#039; input pin or on the availability or absence of CAN traffic on any of the CAN interfaces. The WCU can also be configured to start after a specific time interval from shut-down. The configuration is done in the [[The Portal Administrator View#Power Management|  WCU Configuration]] in the WICE Portal.&lt;br /&gt;
Note that the behaviour of the ignition pin depends on the setting of the START switch on the back of the WCU. If the switch is set to INT the pin will always be active, so that if the WCU is set to&#039;&#039;Wake on ignition&#039;&#039; it will be always on. If the switch is set to EXT, the pin will reflect the current state of the ignition of the vehicle (providing it is correctly installed).&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.93&amp;diff=3869</id>
		<title>New features in v2.93</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.93&amp;diff=3869"/>
		<updated>2025-03-06T11:48:22Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for using labels to control permissions ==&lt;br /&gt;
It is now possible to select resources by labels as an alternative to select resources manually when selecting resources for a permission in [[Roles and permissions]].&lt;br /&gt;
[[File:Labels in permissions1.png|thumb]]&lt;br /&gt;
[[File:Permission label2.png|thumb|Select resources by labels]]&lt;br /&gt;
When a label is selected as in the screenshot to the right, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels.&lt;br /&gt;
&lt;br /&gt;
After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.&lt;br /&gt;
&lt;br /&gt;
== Support for impersonating another user ==&lt;br /&gt;
[[File:Impersonate user.png|thumb|Impersonate user]]&lt;br /&gt;
An admin user can impersonate another user by selecting a user in the [[The Portal Administrator View#The_User_Tab]] and click the new button &amp;quot;Impersonate&amp;quot; as can be seen in the screenshot &amp;quot;Impersonate user&amp;quot;. &lt;br /&gt;
[[File:Impersonating user.png|thumb|Impersonating user]]&lt;br /&gt;
When the button has been clicked, the portal will be reloaded and once logged in again you are now impersonating the selected user. See screenshot &amp;quot;Impersonating user&amp;quot;. &lt;br /&gt;
&lt;br /&gt;
To stop impersonating, one can either click the new &amp;quot;Stop impersonating user&amp;quot; icon next to the red text &amp;quot;Impersonating user&amp;quot; or click the logout icon in the upper right corner of the portal.&lt;br /&gt;
&lt;br /&gt;
== Platform types in WMUs ==&lt;br /&gt;
[[File:Selected platform for new WMU.png|thumb|Select platform for new WMU]]&lt;br /&gt;
When adding a new WMU via the portal GUI it is now mandatory to select the platform for the new WMU as can be seen in the screenshot &amp;quot;Select platform for new WMU&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If the WMU is running WMU version 3.0.0 or above it will also report its platform back to the portal. In the case the reported platform does not match the selected platform a warning will be shown and the selected platform must be changed to the reported before the WCU configuration can be saved.&lt;br /&gt;
[[File:Reported WMU platform does not match selected2.png|thumb|Reported WMU platform does not match selected]]&lt;br /&gt;
See screenshot &amp;quot;Reported WMU platform does not match selected. &lt;br /&gt;
&lt;br /&gt;
== Support for moving a vehicle to a resource group when applying a vehicle template ==&lt;br /&gt;
It is now possible to move a vehicle into a resource group with the help of vehicle templates. For more detailed information on how to use this feature, you can read more [https://wiki.alkit.se/wice293/index.php/Vehicle_templates here].&lt;br /&gt;
&lt;br /&gt;
== Support for MDF file recovery after a WCU crash ==&lt;br /&gt;
[[File:ApplyFileToAllVehicles.png|thumb|Apply File To all Vehicles]]&lt;br /&gt;
From version 2.93, the WCU can recover Signal Reader measurement data after a crash or similar unexpected shut-down. To enable this, there is a new checkbox called &#039;Recover MDF files after unexpected shutdowns&#039; in theSignal Reader module settings. If the checkbox is checked and the WCU crashes, MDF signal data will be recovered  from the temporary signal data storage on the WCU the next time the WCU is started. The recovered MDF file is uploaded to the WICE back-end. Pre-trig logging is not possible to recover.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3868</id>
		<title>WCU platform</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3868"/>
		<updated>2025-03-06T11:34:51Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* DLT module */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Wireless Communication Unit (WCU) is the in-vehicle unit running the WICE WCU software and communicating with the vehicle and the WICE back-end.&lt;br /&gt;
&lt;br /&gt;
WCU:s are identified by a unique text string, which by convention is the MAC address of (one of) the ethernet interfaces in the unit. The WCU id is configured on each WCU (automatically from the MAC address) and is a search parameter available in the WICE Portal web-GUI.&lt;br /&gt;
&lt;br /&gt;
=== WCU Hardware Platform ===&lt;br /&gt;
The following hardware platforms are supported for the WICE WCU:&lt;br /&gt;
&lt;br /&gt;
* Host Mobility MX-4 (T20, T30, T30FR and V61) &lt;br /&gt;
* Fältcom MIIPS Committo &lt;br /&gt;
* Raspberry Pi&lt;br /&gt;
* Nvidia Jetson Xavier&lt;br /&gt;
&lt;br /&gt;
Depending on the specific hardware platform, the WCU supports a number of communication interfaces, such as CAN, LIN, FlexRay and Ethernet and that be configured in different ways using the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
The WCU has the following communication interfaces (some of which are optional):&lt;br /&gt;
&lt;br /&gt;
* a point-to-point (ppp) interface using a 2G/3G/4G mobile data modem&lt;br /&gt;
* optionally, a WiFi wireless LAN interface&lt;br /&gt;
* one to four wired ethernet interfaces.&lt;br /&gt;
* two to six Controller Area Network (CAN) interfaces&lt;br /&gt;
* optionally a FlexRay interface&lt;br /&gt;
* optionally, one or more LIN interfaces&lt;br /&gt;
* one to two USB interfaces.&lt;br /&gt;
&lt;br /&gt;
The unit has the following storage mechanisms:&lt;br /&gt;
&lt;br /&gt;
* internal flash memory for persistent storage&lt;br /&gt;
* removable SD card for temporary storage&lt;br /&gt;
&lt;br /&gt;
The unit has the following power modes:&lt;br /&gt;
&lt;br /&gt;
* running (full functionality available)&lt;br /&gt;
* sleep (suspended state)&lt;br /&gt;
* deep sleep (low-power suspended state)&lt;br /&gt;
&lt;br /&gt;
The WCU platform can also support some limited user-interaction through light-emitting diodes (LED) on the side of the unit. A description of the LEDs is available  [[WCU LEDs|here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Firmware ===&lt;br /&gt;
The WCU firmware is the operating system, device drivers and basic packages required to run the system. The WCU units are delivered with the firmware installed. It can be remotely upgraded from the WICE Portal in a similar way as the WCU Software (see below).&lt;br /&gt;
&lt;br /&gt;
=== WCU Software  ===&lt;br /&gt;
The WCU software is delivered as a self-extracting application installation package, which can be run on the WCU:s manually from a command prompt, using a suitably prepared USB stick, or updated remotely using the WICE Portal mechanism for remote software upgrades.&lt;br /&gt;
&lt;br /&gt;
The WICE solution for remote update of the WCU software works as follows: The Alkit staff member responsible for the WCU software deployment publishes installation packages for supported versions of the WCU software at the WICE Portal, in the WICE back-end server infrastructure. WICE administrators can then select which version of the available WCU software versions should be run on each of the WCUs that are registered in the system (see [[The Portal Administrator View#Edit the WCU Configuration|Edit WCU Configuration]]). This is done by choosing a particular version in a drop-down menu in the WICE Portal in the WCU configuration view. Many WCUs can be configured at the same time.&lt;br /&gt;
Then, whenever a WCU connects to the back-end, a check is made to see whether a different WCU software version (higher or lower version) than the currently installed version for the WCU in question is configured. If so, the installation package is downloaded to the WCU’s solid-state storage over the secure TLS connection that was established when the WCU connected. When the download is finished, the WCU software package will be installed on the WCU. After the installation has finished, the WCU will report back to the WICE back-end infrastructure with the new version of the WCU, so that WICE administrators can keep track of the currently installed software version, as well as the history of software changes.&lt;br /&gt;
A similar process is performed to update the WCU firmware and operating system. When new firmware is installed, the partition where the certificate and configuration files reside is left unaltered.&lt;br /&gt;
&lt;br /&gt;
The WCU software release history is available [[https://wice-sysdoc.alkit.se/index.php/WICE_WCU_Software_Revision_History here]].&lt;br /&gt;
&lt;br /&gt;
==== Extra Bundles ====&lt;br /&gt;
Some WICE software packages, referred to as &#039;extra bundles&#039; are not installed by default. The user needs to select which, if any, extra bundles should be installed on a particular WCU. This is done in the WICE Portal, Edit Configuration. [[Extra bundles|For more information about Extra bundles, click here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Modules ===&lt;br /&gt;
The WCU Modules are the software components of the WCU producing&lt;br /&gt;
measurement data. They are configured through the Configuration Manager, which communicates with the WICE Portal, where the user can access and change the overall WCU configuration and the per-module configurations.&lt;br /&gt;
&lt;br /&gt;
The data capture behavior of the WCU modules is described by a measurement task, downloaded from the WICE Portal by the Task Manager component, which sets up the modules.&lt;br /&gt;
&lt;br /&gt;
The available WCU modules are:  &lt;br /&gt;
* Arcos&lt;br /&gt;
* Area5&lt;br /&gt;
* Audio&lt;br /&gt;
* Blue piraT&lt;br /&gt;
* Canrecorder&lt;br /&gt;
* DLT&lt;br /&gt;
* DoIP&lt;br /&gt;
* ETAS&lt;br /&gt;
* Ethernet capture&lt;br /&gt;
* File fetcher&lt;br /&gt;
* GPS&lt;br /&gt;
* IDC&lt;br /&gt;
* IPEmotion RT&lt;br /&gt;
* LPD&lt;br /&gt;
* M-Log&lt;br /&gt;
* MQTT&lt;br /&gt;
* Rapid Prototyping&lt;br /&gt;
* Signal Reader&lt;br /&gt;
* State-of-Health&lt;br /&gt;
* SWDL&lt;br /&gt;
* Video &lt;br /&gt;
* WCU internals and status&lt;br /&gt;
&lt;br /&gt;
==== Arcos module ====&lt;br /&gt;
The Arcos module makes it possible to use an Arcos data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the Arcos and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== Area5 module ====&lt;br /&gt;
The Area5 module is used to read out ECU memory segments using CCP or XCP. The binary data of the memory segments are uploaded to the back-end where they are translated into parameter sets and signals.  &lt;br /&gt;
&lt;br /&gt;
==== Audio module ====&lt;br /&gt;
The audio module makes it possible to record sound clips from microphones connected to the audio devices of WCUs. Audio can also be streamed in real time from WCUs for live audio monitoring purposes.&lt;br /&gt;
The recording of audio can be triggered by a push button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started or when the trigger condition is fulfilled the audio recording starts, and when the recorder stops, the audio recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Audio sample rate, number of channels (mono or stereo) and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== Blue piraT Module ====&lt;br /&gt;
The Blue piraT module makes it possible to use a Blue piraT logger connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement configuration can be downloaded to the logger and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== CAN Recorder Module ====&lt;br /&gt;
The CAN Recorder Module supports frame logging on the CAN-buses the WCU is connected to. Filters for the ECU identifiers to log can be&lt;br /&gt;
defined in the WICE Portal interface when creating a CAN Recorder measurement task.&lt;br /&gt;
&lt;br /&gt;
==== DLT module ====&lt;br /&gt;
The DLT module supports read-out of Diagnostic Log Trace files. The read-out can be done either using an in-vehicle DLT daemon, or using UDS Service 38 file transfer. See [[DLT Module|DLT module]].&lt;br /&gt;
&lt;br /&gt;
==== DoIP module ====&lt;br /&gt;
The DoIP module makes it possible to establish a tunnel over the Internet to a WCU for synchronous communication using the DoIP protocol.&lt;br /&gt;
In the WCU, the remote DoIP functionality is based on the DoIP daemon &#039;&#039;&#039;doipd&#039;&#039;&#039;, which relays DoIP communication between vehicle and the back-end. &lt;br /&gt;
It also takes care of waking up the vehicle when communication requests are pending. For more information see [[Remote Diagnostics over IP (DoIP)|Remote Diagnostics over IP (DoIP)]].&lt;br /&gt;
&lt;br /&gt;
==== Ethernet Capture Module ====&lt;br /&gt;
The Ethernet Capture module supports logging of ethernet frames on one of the WCU&#039;s ethernet interfaces. Filters can be set (in tcpdump format) for selecting which frames to capture. The result is logged in a pcap file, which is uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== ETAS Module ====&lt;br /&gt;
The ETAS module makes it possible to use an ETAS ES720 measurement system connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement tasks can be downloaded to the ES720 and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== File Fetcher Module ====&lt;br /&gt;
The File Fetcher module supports uploading of files collected from a unit connected to the WCU. &lt;br /&gt;
&lt;br /&gt;
==== GPS Module ====&lt;br /&gt;
The GPS Module reads the position of a WCU at regular intervals and&lt;br /&gt;
reports to the WICE Portal, to support map-based localization of vehicles for the fleet-management service and for the &amp;quot;Plot Route&amp;quot; function of the metrology service.&lt;br /&gt;
&lt;br /&gt;
==== IDC module ====&lt;br /&gt;
The IDC module allows a sequence of diagnostic requests to be sent on the&lt;br /&gt;
in-vehicle network (either CAN or Ethernet), and the responses are collected in a result file. IDC can also read OBD-II PIDs and interpret the responses.&lt;br /&gt;
IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.&lt;br /&gt;
An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].&lt;br /&gt;
&lt;br /&gt;
==== IPEmotion RT ====&lt;br /&gt;
The IPEmotion RT module makes it possible to use an IPEmotion RT data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the logger and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== LPD module ====&lt;br /&gt;
The LPD module supports long term driveline testing using a custom built Android app that connects to the WICE WCU. &lt;br /&gt;
&lt;br /&gt;
==== M-Log module ====&lt;br /&gt;
The M-log module makes it possible to use an M-Log data logger connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the M-Log and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== MQTT module ====&lt;br /&gt;
The MQTT module makes it possible to collect data from another system using an MQTT broker and specifying MQTT topics.&lt;br /&gt;
&lt;br /&gt;
==== Rapid Prototyping module ====&lt;br /&gt;
With the Rapid Prototyping (RP) module, custom software components can be run on the WCU for proof-of-concept testing of new in-vehicle functionality. A Signal Broker API (provided by the Signal Reader module, see below) can be used to easily access in-vehicle signals and parameters. Output data from the RP module is uploaded to the WICE back-end where it is made available in the WICE Portal. The RP module supports both native applications, compiled for the WCU processor architecture, and Node.js applications written in Javascript. The latter is particularly useful for providing in-vehicle GUI functionality.&lt;br /&gt;
&lt;br /&gt;
For more information see [[WICE_RP_How-To]].&lt;br /&gt;
&lt;br /&gt;
==== Signal Reader Module ====&lt;br /&gt;
The Signal Reader module executes a measurement task, monitors and logs time-series signal data and stores the data in an MDF file (Measurement Data&lt;br /&gt;
Format). Signals can be recorded from the vehicle&#039;s internal communication buses (e.g. CAN, LIN, FlexRay). A number of signals internal to the WCU are also available: [[WICE Internal Signals|WICE Internal Signals]]&lt;br /&gt;
&lt;br /&gt;
Signal Reader also supports logging of signals using CCP, XCP and UDS diagnostics. This is sometimes referred to as Active signals.&lt;br /&gt;
&lt;br /&gt;
Triggers are supported, switching between measurement set-ups and starting and stopping recorders. Trigger expression syntax is described [[Signal Reader Trigger Expressions|here]]. Pre- and post-trig recording can be specified, which results in signal data being recorded prior to or subsequent to a trigger condition respectively. Minimum and maximum shot lengths of recorders can also be specified.&lt;br /&gt;
&lt;br /&gt;
==== State of Health Module ====&lt;br /&gt;
The State-of-Health (SoH) module is used to read out a limited data set&lt;br /&gt;
from test vehicles to monitor their operational status. The specific data to be read is configurable from the WICE portal and includes&lt;br /&gt;
position, mileage (odometer), battery voltage, ECU software numbers, Diagnostic Trouble Codes and uptime. The SoH module uses the IDC module to&lt;br /&gt;
service a sequence of diagnostic requests, created by the WICE Portal&lt;br /&gt;
based on which data is requested and the diagnostic database of the vehicle type. Position is accessed from the GPS Module (see below)&lt;br /&gt;
and uptime is accessed from the WCU internal module (see below).&lt;br /&gt;
&lt;br /&gt;
==== SWDL module ====&lt;br /&gt;
The Software Download (SWDL) module makes it possible to download ECU software to connected vehicles for re-programming. The input to the SWDL module is a number of VBF (Versatile Binary Format) files containing the ECU software, and PIN codes for the ECUs to be reprogrammed. Sequence files can also be supplied for pre- and post-programming diagnostics.&lt;br /&gt;
&lt;br /&gt;
==== Video module ====&lt;br /&gt;
The video module makes it possible to record video clips from cameras connected to the WCU. Video can also be streamed in real time from WCUs for live video monitoring purposes.&lt;br /&gt;
The recording of video can be triggered by a push-button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started (i.e. when a trigger condition is fulfilled) the video recording starts, and when the recorder stops, the video recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Video resolution, frame rate and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== WCU internals Module ====&lt;br /&gt;
The WCU internals Module logs useful information about a WCU, including&lt;br /&gt;
uptime, battery voltage (on the WCU power input), and memory usage.&lt;br /&gt;
&lt;br /&gt;
==== WCU Status Module ====&lt;br /&gt;
The WCU status Daemon, statusd,&lt;br /&gt;
monitors the status of the WCU, including all the modules, and&lt;br /&gt;
reports to the WICE Portal. The daemon also provides a common i/o API&lt;br /&gt;
for all modules, including GPS and digital i/o.&lt;br /&gt;
&lt;br /&gt;
=== Power Management ===&lt;br /&gt;
The Power Management settings of the WCU determines how and when the unit is started and shut down. What Power Management mechanisms are available depends on the WCU hardware platform. The following refers to the MX4 platform.&lt;br /&gt;
The MX4 unit can be started and stopped based on the &#039;&#039;ignition&#039;&#039; input pin or on the availability or absence of CAN traffic on any of the CAN interfaces. The WCU can also be configured to start after a specific time interval from shut-down. The configuration is done in the [[The Portal Administrator View#Power Management|  WCU Configuration]] in the WICE Portal.&lt;br /&gt;
Note that the behaviour of the ignition pin depends on the setting of the START switch on the back of the WCU. If the switch is set to INT the pin will always be active, so that if the WCU is set to&#039;&#039;Wake on ignition&#039;&#039; it will be always on. If the switch is set to EXT, the pin will reflect the current state of the ignition of the vehicle (providing it is correctly installed).&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3867</id>
		<title>WCU platform</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3867"/>
		<updated>2025-03-06T11:33:56Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Wireless Communication Unit (WCU) is the in-vehicle unit running the WICE WCU software and communicating with the vehicle and the WICE back-end.&lt;br /&gt;
&lt;br /&gt;
WCU:s are identified by a unique text string, which by convention is the MAC address of (one of) the ethernet interfaces in the unit. The WCU id is configured on each WCU (automatically from the MAC address) and is a search parameter available in the WICE Portal web-GUI.&lt;br /&gt;
&lt;br /&gt;
=== WCU Hardware Platform ===&lt;br /&gt;
The following hardware platforms are supported for the WICE WCU:&lt;br /&gt;
&lt;br /&gt;
* Host Mobility MX-4 (T20, T30, T30FR and V61) &lt;br /&gt;
* Fältcom MIIPS Committo &lt;br /&gt;
* Raspberry Pi&lt;br /&gt;
* Nvidia Jetson Xavier&lt;br /&gt;
&lt;br /&gt;
Depending on the specific hardware platform, the WCU supports a number of communication interfaces, such as CAN, LIN, FlexRay and Ethernet and that be configured in different ways using the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
The WCU has the following communication interfaces (some of which are optional):&lt;br /&gt;
&lt;br /&gt;
* a point-to-point (ppp) interface using a 2G/3G/4G mobile data modem&lt;br /&gt;
* optionally, a WiFi wireless LAN interface&lt;br /&gt;
* one to four wired ethernet interfaces.&lt;br /&gt;
* two to six Controller Area Network (CAN) interfaces&lt;br /&gt;
* optionally a FlexRay interface&lt;br /&gt;
* optionally, one or more LIN interfaces&lt;br /&gt;
* one to two USB interfaces.&lt;br /&gt;
&lt;br /&gt;
The unit has the following storage mechanisms:&lt;br /&gt;
&lt;br /&gt;
* internal flash memory for persistent storage&lt;br /&gt;
* removable SD card for temporary storage&lt;br /&gt;
&lt;br /&gt;
The unit has the following power modes:&lt;br /&gt;
&lt;br /&gt;
* running (full functionality available)&lt;br /&gt;
* sleep (suspended state)&lt;br /&gt;
* deep sleep (low-power suspended state)&lt;br /&gt;
&lt;br /&gt;
The WCU platform can also support some limited user-interaction through light-emitting diodes (LED) on the side of the unit. A description of the LEDs is available  [[WCU LEDs|here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Firmware ===&lt;br /&gt;
The WCU firmware is the operating system, device drivers and basic packages required to run the system. The WCU units are delivered with the firmware installed. It can be remotely upgraded from the WICE Portal in a similar way as the WCU Software (see below).&lt;br /&gt;
&lt;br /&gt;
=== WCU Software  ===&lt;br /&gt;
The WCU software is delivered as a self-extracting application installation package, which can be run on the WCU:s manually from a command prompt, using a suitably prepared USB stick, or updated remotely using the WICE Portal mechanism for remote software upgrades.&lt;br /&gt;
&lt;br /&gt;
The WICE solution for remote update of the WCU software works as follows: The Alkit staff member responsible for the WCU software deployment publishes installation packages for supported versions of the WCU software at the WICE Portal, in the WICE back-end server infrastructure. WICE administrators can then select which version of the available WCU software versions should be run on each of the WCUs that are registered in the system (see [[The Portal Administrator View#Edit the WCU Configuration|Edit WCU Configuration]]). This is done by choosing a particular version in a drop-down menu in the WICE Portal in the WCU configuration view. Many WCUs can be configured at the same time.&lt;br /&gt;
Then, whenever a WCU connects to the back-end, a check is made to see whether a different WCU software version (higher or lower version) than the currently installed version for the WCU in question is configured. If so, the installation package is downloaded to the WCU’s solid-state storage over the secure TLS connection that was established when the WCU connected. When the download is finished, the WCU software package will be installed on the WCU. After the installation has finished, the WCU will report back to the WICE back-end infrastructure with the new version of the WCU, so that WICE administrators can keep track of the currently installed software version, as well as the history of software changes.&lt;br /&gt;
A similar process is performed to update the WCU firmware and operating system. When new firmware is installed, the partition where the certificate and configuration files reside is left unaltered.&lt;br /&gt;
&lt;br /&gt;
The WCU software release history is available [[https://wice-sysdoc.alkit.se/index.php/WICE_WCU_Software_Revision_History here]].&lt;br /&gt;
&lt;br /&gt;
==== Extra Bundles ====&lt;br /&gt;
Some WICE software packages, referred to as &#039;extra bundles&#039; are not installed by default. The user needs to select which, if any, extra bundles should be installed on a particular WCU. This is done in the WICE Portal, Edit Configuration. [[Extra bundles|For more information about Extra bundles, click here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Modules ===&lt;br /&gt;
The WCU Modules are the software components of the WCU producing&lt;br /&gt;
measurement data. They are configured through the Configuration Manager, which communicates with the WICE Portal, where the user can access and change the overall WCU configuration and the per-module configurations.&lt;br /&gt;
&lt;br /&gt;
The data capture behavior of the WCU modules is described by a measurement task, downloaded from the WICE Portal by the Task Manager component, which sets up the modules.&lt;br /&gt;
&lt;br /&gt;
The available WCU modules are:  &lt;br /&gt;
* Arcos&lt;br /&gt;
* Area5&lt;br /&gt;
* Audio&lt;br /&gt;
* Blue piraT&lt;br /&gt;
* Canrecorder&lt;br /&gt;
* DLT&lt;br /&gt;
* DoIP&lt;br /&gt;
* ETAS&lt;br /&gt;
* Ethernet capture&lt;br /&gt;
* File fetcher&lt;br /&gt;
* GPS&lt;br /&gt;
* IDC&lt;br /&gt;
* IPEmotion RT&lt;br /&gt;
* LPD&lt;br /&gt;
* M-Log&lt;br /&gt;
* MQTT&lt;br /&gt;
* Rapid Prototyping&lt;br /&gt;
* Signal Reader&lt;br /&gt;
* State-of-Health&lt;br /&gt;
* SWDL&lt;br /&gt;
* Video &lt;br /&gt;
* WCU internals and status&lt;br /&gt;
&lt;br /&gt;
==== Arcos module ====&lt;br /&gt;
The Arcos module makes it possible to use an Arcos data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the Arcos and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== Area5 module ====&lt;br /&gt;
The Area5 module is used to read out ECU memory segments using CCP or XCP. The binary data of the memory segments are uploaded to the back-end where they are translated into parameter sets and signals.  &lt;br /&gt;
&lt;br /&gt;
==== Audio module ====&lt;br /&gt;
The audio module makes it possible to record sound clips from microphones connected to the audio devices of WCUs. Audio can also be streamed in real time from WCUs for live audio monitoring purposes.&lt;br /&gt;
The recording of audio can be triggered by a push button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started or when the trigger condition is fulfilled the audio recording starts, and when the recorder stops, the audio recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Audio sample rate, number of channels (mono or stereo) and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== Blue piraT Module ====&lt;br /&gt;
The Blue piraT module makes it possible to use a Blue piraT logger connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement configuration can be downloaded to the logger and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== CAN Recorder Module ====&lt;br /&gt;
The CAN Recorder Module supports frame logging on the CAN-buses the WCU is connected to. Filters for the ECU identifiers to log can be&lt;br /&gt;
defined in the WICE Portal interface when creating a CAN Recorder measurement task.&lt;br /&gt;
&lt;br /&gt;
==== DLT module ====&lt;br /&gt;
The DLT module supports read-out of Diagnostic Log Trace files. See [[DLT Module|DLT module]].&lt;br /&gt;
&lt;br /&gt;
==== DoIP module ====&lt;br /&gt;
The DoIP module makes it possible to establish a tunnel over the Internet to a WCU for synchronous communication using the DoIP protocol.&lt;br /&gt;
In the WCU, the remote DoIP functionality is based on the DoIP daemon &#039;&#039;&#039;doipd&#039;&#039;&#039;, which relays DoIP communication between vehicle and the back-end. &lt;br /&gt;
It also takes care of waking up the vehicle when communication requests are pending. For more information see [[Remote Diagnostics over IP (DoIP)|Remote Diagnostics over IP (DoIP)]].&lt;br /&gt;
&lt;br /&gt;
==== Ethernet Capture Module ====&lt;br /&gt;
The Ethernet Capture module supports logging of ethernet frames on one of the WCU&#039;s ethernet interfaces. Filters can be set (in tcpdump format) for selecting which frames to capture. The result is logged in a pcap file, which is uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== ETAS Module ====&lt;br /&gt;
The ETAS module makes it possible to use an ETAS ES720 measurement system connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement tasks can be downloaded to the ES720 and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== File Fetcher Module ====&lt;br /&gt;
The File Fetcher module supports uploading of files collected from a unit connected to the WCU. &lt;br /&gt;
&lt;br /&gt;
==== GPS Module ====&lt;br /&gt;
The GPS Module reads the position of a WCU at regular intervals and&lt;br /&gt;
reports to the WICE Portal, to support map-based localization of vehicles for the fleet-management service and for the &amp;quot;Plot Route&amp;quot; function of the metrology service.&lt;br /&gt;
&lt;br /&gt;
==== IDC module ====&lt;br /&gt;
The IDC module allows a sequence of diagnostic requests to be sent on the&lt;br /&gt;
in-vehicle network (either CAN or Ethernet), and the responses are collected in a result file. IDC can also read OBD-II PIDs and interpret the responses.&lt;br /&gt;
IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.&lt;br /&gt;
An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].&lt;br /&gt;
&lt;br /&gt;
==== IPEmotion RT ====&lt;br /&gt;
The IPEmotion RT module makes it possible to use an IPEmotion RT data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the logger and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== LPD module ====&lt;br /&gt;
The LPD module supports long term driveline testing using a custom built Android app that connects to the WICE WCU. &lt;br /&gt;
&lt;br /&gt;
==== M-Log module ====&lt;br /&gt;
The M-log module makes it possible to use an M-Log data logger connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the M-Log and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== MQTT module ====&lt;br /&gt;
The MQTT module makes it possible to collect data from another system using an MQTT broker and specifying MQTT topics.&lt;br /&gt;
&lt;br /&gt;
==== Rapid Prototyping module ====&lt;br /&gt;
With the Rapid Prototyping (RP) module, custom software components can be run on the WCU for proof-of-concept testing of new in-vehicle functionality. A Signal Broker API (provided by the Signal Reader module, see below) can be used to easily access in-vehicle signals and parameters. Output data from the RP module is uploaded to the WICE back-end where it is made available in the WICE Portal. The RP module supports both native applications, compiled for the WCU processor architecture, and Node.js applications written in Javascript. The latter is particularly useful for providing in-vehicle GUI functionality.&lt;br /&gt;
&lt;br /&gt;
For more information see [[WICE_RP_How-To]].&lt;br /&gt;
&lt;br /&gt;
==== Signal Reader Module ====&lt;br /&gt;
The Signal Reader module executes a measurement task, monitors and logs time-series signal data and stores the data in an MDF file (Measurement Data&lt;br /&gt;
Format). Signals can be recorded from the vehicle&#039;s internal communication buses (e.g. CAN, LIN, FlexRay). A number of signals internal to the WCU are also available: [[WICE Internal Signals|WICE Internal Signals]]&lt;br /&gt;
&lt;br /&gt;
Signal Reader also supports logging of signals using CCP, XCP and UDS diagnostics. This is sometimes referred to as Active signals.&lt;br /&gt;
&lt;br /&gt;
Triggers are supported, switching between measurement set-ups and starting and stopping recorders. Trigger expression syntax is described [[Signal Reader Trigger Expressions|here]]. Pre- and post-trig recording can be specified, which results in signal data being recorded prior to or subsequent to a trigger condition respectively. Minimum and maximum shot lengths of recorders can also be specified.&lt;br /&gt;
&lt;br /&gt;
==== State of Health Module ====&lt;br /&gt;
The State-of-Health (SoH) module is used to read out a limited data set&lt;br /&gt;
from test vehicles to monitor their operational status. The specific data to be read is configurable from the WICE portal and includes&lt;br /&gt;
position, mileage (odometer), battery voltage, ECU software numbers, Diagnostic Trouble Codes and uptime. The SoH module uses the IDC module to&lt;br /&gt;
service a sequence of diagnostic requests, created by the WICE Portal&lt;br /&gt;
based on which data is requested and the diagnostic database of the vehicle type. Position is accessed from the GPS Module (see below)&lt;br /&gt;
and uptime is accessed from the WCU internal module (see below).&lt;br /&gt;
&lt;br /&gt;
==== SWDL module ====&lt;br /&gt;
The Software Download (SWDL) module makes it possible to download ECU software to connected vehicles for re-programming. The input to the SWDL module is a number of VBF (Versatile Binary Format) files containing the ECU software, and PIN codes for the ECUs to be reprogrammed. Sequence files can also be supplied for pre- and post-programming diagnostics.&lt;br /&gt;
&lt;br /&gt;
==== Video module ====&lt;br /&gt;
The video module makes it possible to record video clips from cameras connected to the WCU. Video can also be streamed in real time from WCUs for live video monitoring purposes.&lt;br /&gt;
The recording of video can be triggered by a push-button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started (i.e. when a trigger condition is fulfilled) the video recording starts, and when the recorder stops, the video recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Video resolution, frame rate and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== WCU internals Module ====&lt;br /&gt;
The WCU internals Module logs useful information about a WCU, including&lt;br /&gt;
uptime, battery voltage (on the WCU power input), and memory usage.&lt;br /&gt;
&lt;br /&gt;
==== WCU Status Module ====&lt;br /&gt;
The WCU status Daemon, statusd,&lt;br /&gt;
monitors the status of the WCU, including all the modules, and&lt;br /&gt;
reports to the WICE Portal. The daemon also provides a common i/o API&lt;br /&gt;
for all modules, including GPS and digital i/o.&lt;br /&gt;
&lt;br /&gt;
=== Power Management ===&lt;br /&gt;
The Power Management settings of the WCU determines how and when the unit is started and shut down. What Power Management mechanisms are available depends on the WCU hardware platform. The following refers to the MX4 platform.&lt;br /&gt;
The MX4 unit can be started and stopped based on the &#039;&#039;ignition&#039;&#039; input pin or on the availability or absence of CAN traffic on any of the CAN interfaces. The WCU can also be configured to start after a specific time interval from shut-down. The configuration is done in the [[The Portal Administrator View#Power Management|  WCU Configuration]] in the WICE Portal.&lt;br /&gt;
Note that the behaviour of the ignition pin depends on the setting of the START switch on the back of the WCU. If the switch is set to INT the pin will always be active, so that if the WCU is set to&#039;&#039;Wake on ignition&#039;&#039; it will be always on. If the switch is set to EXT, the pin will reflect the current state of the ignition of the vehicle (providing it is correctly installed).&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WICE_Cybersecurity&amp;diff=3839</id>
		<title>WICE Cybersecurity</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WICE_Cybersecurity&amp;diff=3839"/>
		<updated>2025-02-19T11:38:58Z</updated>

		<summary type="html">&lt;p&gt;Mathias: Created page with &amp;quot;WICE has a large number of cybersecurity mechanisms implemented in response to threats. Threats are identified in a TARA procedure and potential weaknesses in WICE are addressed.  Alkit maintains a publicly accessible Vulnerability disclosure programme that allows for the disclosure of Vulnerabilities discovered by researchers and other external actors or entities. Contact [https://www.alkit.se/index.php/contacts Alkit Communications] to receive information required to u...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;WICE has a large number of cybersecurity mechanisms implemented in response to threats. Threats are identified in a TARA procedure and potential weaknesses in WICE are addressed.&lt;br /&gt;
&lt;br /&gt;
Alkit maintains a publicly accessible Vulnerability disclosure programme that allows for the disclosure of Vulnerabilities discovered by researchers and other external actors or entities. Contact [https://www.alkit.se/index.php/contacts Alkit Communications] to receive information required to utilise the disclosure programme.&lt;br /&gt;
&lt;br /&gt;
=== WICE Cybersecurity Approach ===&lt;br /&gt;
The high level approach is to secure the back-end and the WCUs and provide a secure channel between them to ensure confidentiality and integrity of the system.&lt;br /&gt;
&lt;br /&gt;
=== Access control mechanism ===&lt;br /&gt;
The WICE system has a comprehensive Access Control framework (configured in the WICE Portal) to control which user has access to which WCU.&lt;br /&gt;
&lt;br /&gt;
=== Secure communication mechanism ===&lt;br /&gt;
The WICE system relies on a secure communication mechanism based on TLS 1.3 and a PKI for communication between WCUs and the WICE back-end.&lt;br /&gt;
&lt;br /&gt;
The WCU communicates with the WICE-back-end using the secure TLS-based tunnel, allowing configurations of the WCUs. The access control of the PKI solution is based on X.509 certificates identifying the endpoints of communication (WCU and WICE back-end). Only WCUs with a valid certificate can connect to the WICE back-end and is therefore an access control mechanism that ensures only authorised WICE users can access a WCU.&lt;br /&gt;
&lt;br /&gt;
=== Authentication mechanism ===&lt;br /&gt;
The WICE system authenticates all users when logging in to the WICE Portal front-end user interface. A role-based access control framework is used to configure which WICE user has access to different resources, including WCUs. A specific user that has been assigned credentials to a specific WCU can then access the WCU by means of the secure TLS-based connection between the WCU and the back-end, provided the WCU is properly configured and authenticated through the PKI.&lt;br /&gt;
&lt;br /&gt;
=== Secure update mechanism ===&lt;br /&gt;
The WICE system supports remote updates of the WCU software, including firmware. The software update mechanism allows an authenticated WICE user with the proper access rights to select a new software version to be installed on one or more WCUs through the WICE Portal user interface. The selected software will be downloaded to the WCU(s) over a secure channel (TLS tunnel), verified for integrity, and installed on the WCU.&lt;br /&gt;
&lt;br /&gt;
=== Resilience mechanism ===&lt;br /&gt;
The WICE system uses resilience mechanisms to mitigate the effects of Denial of Service (DoS) Attacks on the network interfaces of the WCU and return the WCU to a defined state after the attack.&lt;br /&gt;
&lt;br /&gt;
=== Input validation ===&lt;br /&gt;
The WICE system validates all input received via external interfaces if the input has potential impact on security assets and/or network assets.&lt;br /&gt;
&lt;br /&gt;
=== Vulnerability Monitoring ===&lt;br /&gt;
Alkit maintains a publicly accessible Vulnerability disclosure programme that allows for the disclosure of Vulnerabilities discovered by researchers and other external actors or entities. Contact [https://www.alkit.se/index.php/contacts Alkit Communications] to receive information required to utilise the disclosure programme.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WCU_authentication_token&amp;diff=3742</id>
		<title>WCU authentication token</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WCU_authentication_token&amp;diff=3742"/>
		<updated>2024-11-29T13:11:53Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;float:right; margin-left: 10px;&amp;quot;&lt;br /&gt;
| &#039;&#039;&#039;WCU version&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
| 2.46 and later&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The WCU configuration (reached via the [[Vehicles|Vehicles panel]]) contains the possibility to administer the WCU authentication token used for USB sticks on the WCU.  &lt;br /&gt;
&lt;br /&gt;
Press the &#039;&#039;&#039;New UUID&#039;&#039;&#039; button, shown in the Figure &amp;quot;WCU Configuration: Authentication Token&amp;quot;, to generate such an authentication token. Remember to click &#039;&#039;&#039;Save&#039;&#039;&#039; to save the generated token.&lt;br /&gt;
&lt;br /&gt;
To use the generated token for data offload to a USB stick, put the token in a file called wice-access-token.txt i a directory called /wice/wcu_id, for instance&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/wice/04-1B-94-00-1D-2A/wice-access-token.txt&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When a USB stick thus prepared is inserted in a WCU with the corresponding id, data will be offloaded to the USB stick. &lt;br /&gt;
[[File:WcuConfigAuthToken.png|left|thumb|WCU Configuration: Authentication Token]]&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3683</id>
		<title>WCU platform</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WCU_platform&amp;diff=3683"/>
		<updated>2024-09-05T11:53:30Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* WCU Modules */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Wireless Communication Unit (WCU) is the in-vehicle unit running the WICE WCU software and communicating with the vehicle and the WICE back-end.&lt;br /&gt;
&lt;br /&gt;
WCU:s are identified by a unique text string, which by convention is the MAC address of (one of) the ethernet interfaces in the unit. The WCU id is configured on each WCU (automatically from the MAC address) and is a search parameter available in the WICE Portal web-GUI.&lt;br /&gt;
&lt;br /&gt;
=== WCU Hardware Platform ===&lt;br /&gt;
The following hardware platforms are supported for the WICE WCU:&lt;br /&gt;
&lt;br /&gt;
* Host Mobility MX-4 (T20, T30, T30FR and V61) &lt;br /&gt;
* Fältcom MIIPS Committo &lt;br /&gt;
* Raspberry Pi&lt;br /&gt;
* Nvidia Jetson Xavier&lt;br /&gt;
&lt;br /&gt;
Depending on the specific hardware platform, the WCU supports a number of communication interfaces, such as CAN, LIN, FlexRay and Ethernet and that be configured in different ways using the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
The WCU platform can also support some limited user-interaction through light-emitting diodes (LED) on the side of the unit. A description of the LEDs is available  [[WCU LEDs|here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Firmware ===&lt;br /&gt;
The WCU firmware is the operating system, device drivers and basic packages required to run the system. The WCU units are delivered with the firmware installed. It can be remotely upgraded from the WICE Portal in a similar way as the WCU Software (see below).&lt;br /&gt;
&lt;br /&gt;
=== WCU Software  ===&lt;br /&gt;
The WCU software is delivered as a self-extracting application installation package, which can be run on the WCU:s manually from a command prompt, using a suitably prepared USB stick, or updated remotely using the WICE Portal mechanism for remote software upgrades.&lt;br /&gt;
&lt;br /&gt;
The WICE solution for remote update of the WCU software works as follows: The Alkit staff member responsible for the WCU software deployment publishes installation packages for supported versions of the WCU software at the WICE Portal, in the WICE back-end server infrastructure. WICE administrators can then select which version of the available WCU software versions should be run on each of the WCUs that are registered in the system (see [[The Portal Administrator View#Edit the WCU Configuration|Edit WCU Configuration]]). This is done by choosing a particular version in a drop-down menu in the WICE Portal in the WCU configuration view. Many WCUs can be configured at the same time.&lt;br /&gt;
Then, whenever a WCU connects to the back-end, a check is made to see whether a different WCU software version (higher or lower version) than the currently installed version for the WCU in question is configured. If so, the installation package is downloaded to the WCU’s solid-state storage over the secure TLS connection that was established when the WCU connected. When the download is finished, the WCU software package will be installed on the WCU. After the installation has finished, the WCU will report back to the WICE back-end infrastructure with the new version of the WCU, so that WICE administrators can keep track of the currently installed software version, as well as the history of software changes.&lt;br /&gt;
A similar process is performed to update the WCU firmware and operating system. When new firmware is installed, the partition where the certificate and configuration files reside is left unaltered.&lt;br /&gt;
&lt;br /&gt;
The WCU software release history is available [[https://wice-sysdoc.alkit.se/index.php/WICE_WCU_Software_Revision_History here]].&lt;br /&gt;
&lt;br /&gt;
==== Extra Bundles ====&lt;br /&gt;
Some WICE software packages, referred to as &#039;extra bundles&#039; are not installed by default. The user needs to select which, if any, extra bundles should be installed on a particular WCU. This is done in the WICE Portal, Edit Configuration. [[Extra bundles|For more information about Extra bundles, click here]].&lt;br /&gt;
&lt;br /&gt;
=== WCU Modules ===&lt;br /&gt;
The WCU Modules are the software components of the WCU producing&lt;br /&gt;
measurement data. They are configured through the Configuration Manager, which communicates with the WICE Portal, where the user can access and change the overall WCU configuration and the per-module configurations.&lt;br /&gt;
&lt;br /&gt;
The data capture behavior of the WCU modules is described by a measurement task, downloaded from the WICE Portal by the Task Manager component, which sets up the modules.&lt;br /&gt;
&lt;br /&gt;
The available WCU modules are:  &lt;br /&gt;
* Arcos&lt;br /&gt;
* Area5&lt;br /&gt;
* Audio&lt;br /&gt;
* Blue piraT&lt;br /&gt;
* Canrecorder&lt;br /&gt;
* DLT&lt;br /&gt;
* DoIP&lt;br /&gt;
* ETAS&lt;br /&gt;
* Ethernet capture&lt;br /&gt;
* File fetcher&lt;br /&gt;
* GPS&lt;br /&gt;
* IDC&lt;br /&gt;
* IPEmotion RT&lt;br /&gt;
* LPD&lt;br /&gt;
* M-Log&lt;br /&gt;
* MQTT&lt;br /&gt;
* Rapid Prototyping&lt;br /&gt;
* Signal Reader&lt;br /&gt;
* State-of-Health&lt;br /&gt;
* SWDL&lt;br /&gt;
* Video &lt;br /&gt;
* WCU internals and status&lt;br /&gt;
&lt;br /&gt;
==== Arcos module ====&lt;br /&gt;
The Arcos module makes it possible to use an Arcos data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the Arcos and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== Area5 module ====&lt;br /&gt;
The Area5 module is used to read out ECU memory segments using CCP or XCP. The binary data of the memory segments are uploaded to the back-end where they are translated into parameter sets and signals.  &lt;br /&gt;
&lt;br /&gt;
==== Audio module ====&lt;br /&gt;
The audio module makes it possible to record sound clips from microphones connected to the audio devices of WCUs. Audio can also be streamed in real time from WCUs for live audio monitoring purposes.&lt;br /&gt;
The recording of audio can be triggered by a push button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started or when the trigger condition is fulfilled the audio recording starts, and when the recorder stops, the audio recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Audio sample rate, number of channels (mono or stereo) and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== Blue piraT Module ====&lt;br /&gt;
The Blue piraT module makes it possible to use a Blue piraT logger connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement configuration can be downloaded to the logger and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== CAN Recorder Module ====&lt;br /&gt;
The CAN Recorder Module supports frame logging on the CAN-buses the WCU is connected to. Filters for the ECU identifiers to log can be&lt;br /&gt;
defined in the WICE Portal interface when creating a CAN Recorder measurement task.&lt;br /&gt;
&lt;br /&gt;
==== DLT module ====&lt;br /&gt;
The DLT module supports read-out of Diagnostic Log Trace files. See [[DLT Module|DLT module]].&lt;br /&gt;
&lt;br /&gt;
==== DoIP module ====&lt;br /&gt;
The DoIP module makes it possible to establish a tunnel over the Internet to a WCU for synchronous communication using the DoIP protocol.&lt;br /&gt;
In the WCU, the remote DoIP functionality is based on the DoIP daemon &#039;&#039;&#039;doipd&#039;&#039;&#039;, which relays DoIP communication between vehicle and the back-end. &lt;br /&gt;
It also takes care of waking up the vehicle when communication requests are pending. For more information see [[Remote Diagnostics over IP (DoIP)|Remote Diagnostics over IP (DoIP)]].&lt;br /&gt;
&lt;br /&gt;
==== Ethernet Capture Module ====&lt;br /&gt;
The Ethernet Capture module supports logging of ethernet frames on one of the WCU&#039;s ethernet interfaces. Filters can be set (in tcpdump format) for selecting which frames to capture. The result is logged in a pcap file, which is uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== ETAS Module ====&lt;br /&gt;
The ETAS module makes it possible to use an ETAS ES720 measurement system connected to the WCU through an Ethernet port.&lt;br /&gt;
Measurement tasks can be downloaded to the ES720 and measurement data can be offloaded and uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
==== File Fetcher Module ====&lt;br /&gt;
The File Fetcher module supports uploading of files collected from a unit connected to the WCU. &lt;br /&gt;
&lt;br /&gt;
==== GPS Module ====&lt;br /&gt;
The GPS Module reads the position of a WCU at regular intervals and&lt;br /&gt;
reports to the WICE Portal, to support map-based localization of vehicles for the fleet-management service and for the &amp;quot;Plot Route&amp;quot; function of the metrology service.&lt;br /&gt;
&lt;br /&gt;
==== IDC module ====&lt;br /&gt;
The IDC module allows a sequence of diagnostic requests to be sent on the&lt;br /&gt;
in-vehicle network (either CAN or Ethernet), and the responses are collected in a result file. IDC can also read OBD-II PIDs and interpret the responses.&lt;br /&gt;
IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.&lt;br /&gt;
An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].&lt;br /&gt;
&lt;br /&gt;
==== IPEmotion RT ====&lt;br /&gt;
The IPEmotion RT module makes it possible to use an IPEmotion RT data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the logger and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== LPD module ====&lt;br /&gt;
The LPD module supports long term driveline testing using a custom built Android app that connects to the WICE WCU. &lt;br /&gt;
&lt;br /&gt;
==== M-Log module ====&lt;br /&gt;
The M-log module makes it possible to use an M-Log data logger connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the M-Log and data can be offloaded and uploaded to the portal.&lt;br /&gt;
&lt;br /&gt;
==== MQTT module ====&lt;br /&gt;
The MQTT module makes it possible to collect data from another system using an MQTT broker and specifying MQTT topics.&lt;br /&gt;
&lt;br /&gt;
==== Rapid Prototyping module ====&lt;br /&gt;
With the Rapid Prototyping (RP) module, custom software components can be run on the WCU for proof-of-concept testing of new in-vehicle functionality. A Signal Broker API (provided by the Signal Reader module, see below) can be used to easily access in-vehicle signals and parameters. Output data from the RP module is uploaded to the WICE back-end where it is made available in the WICE Portal. The RP module supports both native applications, compiled for the WCU processor architecture, and Node.js applications written in Javascript. The latter is particularly useful for providing in-vehicle GUI functionality.&lt;br /&gt;
&lt;br /&gt;
For more information see [[WICE_RP_How-To]].&lt;br /&gt;
&lt;br /&gt;
==== Signal Reader Module ====&lt;br /&gt;
The Signal Reader module executes a measurement task, monitors and logs time-series signal data and stores the data in an MDF file (Measurement Data&lt;br /&gt;
Format). Signals can be recorded from the vehicle&#039;s internal communication buses (e.g. CAN, LIN, FlexRay). A number of signals internal to the WCU are also available: [[WICE Internal Signals|WICE Internal Signals]]&lt;br /&gt;
&lt;br /&gt;
Signal Reader also supports logging of signals using CCP, XCP and UDS diagnostics. This is sometimes referred to as Active signals.&lt;br /&gt;
&lt;br /&gt;
Triggers are supported, switching between measurement set-ups and starting and stopping recorders. Trigger expression syntax is described [[Signal Reader Trigger Expressions|here]]. Pre- and post-trig recording can be specified, which results in signal data being recorded prior to or subsequent to a trigger condition respectively. Minimum and maximum shot lengths of recorders can also be specified.&lt;br /&gt;
&lt;br /&gt;
==== State of Health Module ====&lt;br /&gt;
The State-of-Health (SoH) module is used to read out a limited data set&lt;br /&gt;
from test vehicles to monitor their operational status. The specific data to be read is configurable from the WICE portal and includes&lt;br /&gt;
position, mileage (odometer), battery voltage, ECU software numbers, Diagnostic Trouble Codes and uptime. The SoH module uses the IDC module to&lt;br /&gt;
service a sequence of diagnostic requests, created by the WICE Portal&lt;br /&gt;
based on which data is requested and the diagnostic database of the vehicle type. Position is accessed from the GPS Module (see below)&lt;br /&gt;
and uptime is accessed from the WCU internal module (see below).&lt;br /&gt;
&lt;br /&gt;
==== SWDL module ====&lt;br /&gt;
The Software Download (SWDL) module makes it possible to download ECU software to connected vehicles for re-programming. The input to the SWDL module is a number of VBF (Versatile Binary Format) files containing the ECU software, and PIN codes for the ECUs to be reprogrammed. Sequence files can also be supplied for pre- and post-programming diagnostics.&lt;br /&gt;
&lt;br /&gt;
==== Video module ====&lt;br /&gt;
The video module makes it possible to record video clips from cameras connected to the WCU. Video can also be streamed in real time from WCUs for live video monitoring purposes.&lt;br /&gt;
The recording of video can be triggered by a push-button connected to the WCU, or from the Signal Reader module by specifying a recorder name or a trigger expression. In the latter case, when the corresponding Signal Reader recorder is started (i.e. when a trigger condition is fulfilled) the video recording starts, and when the recorder stops, the video recording does as well. Pre-trig buffering is supported.&lt;br /&gt;
Video resolution, frame rate and compression format can be specified in the module configuration.&lt;br /&gt;
&lt;br /&gt;
==== WCU internals Module ====&lt;br /&gt;
The WCU internals Module logs useful information about a WCU, including&lt;br /&gt;
uptime, battery voltage (on the WCU power input), and memory usage.&lt;br /&gt;
&lt;br /&gt;
==== WCU Status Module ====&lt;br /&gt;
The WCU status Daemon, statusd,&lt;br /&gt;
monitors the status of the WCU, including all the modules, and&lt;br /&gt;
reports to the WICE Portal. The daemon also provides a common i/o API&lt;br /&gt;
for all modules, including GPS and digital i/o.&lt;br /&gt;
&lt;br /&gt;
=== Power Management ===&lt;br /&gt;
The Power Management settings of the WCU determines how and when the unit is started and shut down. What Power Management mechanisms are available depends on the WCU hardware platform. The following refers to the MX4 platform.&lt;br /&gt;
The MX4 unit can be started and stopped based on the &#039;&#039;ignition&#039;&#039; input pin or on the availability or absence of CAN traffic on any of the CAN interfaces. The WCU can also be configured to start after a specific time interval from shut-down. The configuration is done in the [[The Portal Administrator View#Power Management|  WCU Configuration]] in the WICE Portal.&lt;br /&gt;
Note that the behaviour of the ignition pin depends on the setting of the START switch on the back of the WCU. If the switch is set to INT the pin will always be active, so that if the WCU is set to&#039;&#039;Wake on ignition&#039;&#039; it will be always on. If the switch is set to EXT, the pin will reflect the current state of the ignition of the vehicle (providing it is correctly installed).&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=3682</id>
		<title>Signal Reader Trigger Expressions</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=Signal_Reader_Trigger_Expressions&amp;diff=3682"/>
		<updated>2024-08-28T06:43:07Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.&lt;br /&gt;
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!=&lt;br /&gt;
|Tests for equality. Syntax: expression = expression&lt;br /&gt;
|-&lt;br /&gt;
!!=&lt;br /&gt;
|Tests for inequality. Syntax: expression != expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;&lt;br /&gt;
|Tests for left side of expression being less than right side. Syntax: expression &amp;lt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;&lt;br /&gt;
|Tests for left side of expression being greater than right side. Syntax: expression &amp;gt; expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;lt;=&lt;br /&gt;
|Tests for left side of expression being less or equal to right side. Syntax: expression &amp;lt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!&amp;gt;=&lt;br /&gt;
|Tests for left side of expression being greater or equal to right side. Syntax: expression &amp;gt;= expression&lt;br /&gt;
|-&lt;br /&gt;
!AND&lt;br /&gt;
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!OR&lt;br /&gt;
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression&lt;br /&gt;
|-&lt;br /&gt;
!NOT&lt;br /&gt;
|Logical negation of boolean expression. Syntax: NOT(boolean expression)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE&lt;br /&gt;
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP&lt;br /&gt;
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN&lt;br /&gt;
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_BY&lt;br /&gt;
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_UP_BY&lt;br /&gt;
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_DOWN_BY&lt;br /&gt;
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)&lt;br /&gt;
|-&lt;br /&gt;
!CHANGE_FROM_TO&lt;br /&gt;
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)&lt;br /&gt;
|-&lt;br /&gt;
!TIMER&lt;br /&gt;
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)&lt;br /&gt;
|-&lt;br /&gt;
!EXPR_TIMER&lt;br /&gt;
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)&lt;br /&gt;
|-&lt;br /&gt;
!TIME_COUNTER&lt;br /&gt;
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!SAMPLE_COUNTER&lt;br /&gt;
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!EVERY&lt;br /&gt;
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)&lt;br /&gt;
|-&lt;br /&gt;
!MOVAV&lt;br /&gt;
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)&lt;br /&gt;
|-&lt;br /&gt;
!ABS&lt;br /&gt;
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)&lt;br /&gt;
|-&lt;br /&gt;
!MIN&lt;br /&gt;
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MAX&lt;br /&gt;
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!MEAN&lt;br /&gt;
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)&lt;br /&gt;
|-&lt;br /&gt;
!LOSS_OF_SIGNAL&lt;br /&gt;
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.87&amp;diff=3557</id>
		<title>New features in v2.87</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.87&amp;diff=3557"/>
		<updated>2024-01-03T14:16:05Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Initial Support for MDF Version 4.1 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Support for Vehicle Communication Forwarder ==&lt;br /&gt;
If enabled in the Portal, it is now possible to add and configure a Vehicle Communication Forwarder to a WCU from Edit Configuration under the  [[I/O configurations#Add CAN channels|I/O Configuration tab]]. If both WMUs and Vehicle Communication Forwarder are enabled in the portal, only Vehicle Communication Forwarder will be shown. Read more about Vehicle Communication Forwarder [[Vehicle Communication Forwarder|here]].&lt;br /&gt;
&lt;br /&gt;
== Assignment Review Support ==&lt;br /&gt;
When having assignments that are delicate in the sense that those will be run on many vehicles or of other reasons, there is now support to appoint one or several reviewers of the assignment. Those reviewers can then approve or reject the assignment for the original editor to fix any problems. In addition to the review process of assignments, there is support to require that only reviewed assignments can be added to resource groups or WCU:s. Read more about the review process [[Review assignment process|here]] and how to enforce that reviewed assignments on resources for WCUs [https://wiki.alkit.se/wice287/index.php/The_Portal_Administrator_View#The_Edit_WCU_Dialog here] and resource groups [[The Portal Administrator View#Approved Assignments|here]].&lt;br /&gt;
&lt;br /&gt;
== Initial Support for MDF Version 4.1 ==&lt;br /&gt;
There is support to search and download MDF files for version 4.1 in the result files panel. Support to preview such files will come later. In the WCU software, there is support for generating MDF files of version 4.1.1, in addition to the previously available 3.x versions. The MDF version is selected in the module settings for Signal Reader.&lt;br /&gt;
&lt;br /&gt;
== Improved Handling of Default Resource Group Labels ==&lt;br /&gt;
Possible to select if default label should remove from the WCU or/and Vehicle when disconnecting from the group. Also possible to default labels will affect current resources in the resource group. Read more [[Edit default labels window|here]].&lt;br /&gt;
&lt;br /&gt;
== Support for Assignment Validation ==&lt;br /&gt;
When creating a signal reader assignment in the editor it is possible to make some common mistake that can affect the vehicle&#039;s behavior. If the user tries to save an assignment with this type of mistake the user will be informed and then take action after it. Read more about signal reader editor [[Signal Reader Assignment Editor|here]].&lt;br /&gt;
&lt;br /&gt;
== Record Result Files Announced to Third Parties ==&lt;br /&gt;
A column named &#039;Announced On&#039; has been added in the result files panel to track when the result file was announced. Additionally, two labels have been introduced on the task to monitor the number of announced files called &#039;announced_files&#039; and the date of the last announcement called &#039;announced_on&amp;quot;. These labels are visible in the tasks panel. Read more about it [https://wiki.alkit.se/wice287/index.php/Creating_a_Task#Announce_result_file_availability here].&lt;br /&gt;
&lt;br /&gt;
== Support to Edit Values on Labels on Tasks ==&lt;br /&gt;
When an assignment is generated with associated labels, it is now possible to modify the values of these labels in the View Task window. Read more about it [https://wiki.alkit.se/wice287/index.php/Tasks_Tab#Task_Options here]. &lt;br /&gt;
&lt;br /&gt;
== WCU Connected Column in Vehicles Panel has Better Mixed Time Format ==&lt;br /&gt;
The column &#039;Connected&#039; in the Vehicles panel has an improved time format presentation. Earlier, it simply showed the number of minutes since a WCU last connected to the portal. This quickly became difficult to use and you had to move the pointer over the cell in order to get a hover message saying the actual date. Now, a mixed format based on how long the WCU connected with the portal is used. Up to a month since the last connected time is shown as, e.g. &#039;7d3h11m&#039;. When the time exceeds a month, the date is shown. Also, filtering is made using the format &#039;7d3h11m&#039;. Read more about this here.&lt;br /&gt;
&lt;br /&gt;
== Support for New Permission to Create Vehicles ==&lt;br /&gt;
There is now a Vehicle Create Permission, which enables non-admin users to create vehicles in the vehicles tab. Additionally, vehicles without a WCU connected will now show up in the vehicles tab for users with this permission. &lt;br /&gt;
&lt;br /&gt;
Read more about creating vehicles [[The Portal Administrator View#Add Vehicle Dialog|here]].&lt;br /&gt;
&lt;br /&gt;
== Support for New Permission to Connect/Disconnect WCU:s and Vehicles in the Portal ==&lt;br /&gt;
There is now a WCU Connect Permission, which enables non-admin users to connect WCUs to vehicles. Read more about connecting WCUs to vehicles [[The Portal Administrator View#The Administration Tab|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved Task Search Performance ==&lt;br /&gt;
Under some circumstances the search i the tasks panel could be lagging for a few seconds and this is now improved.&lt;br /&gt;
&lt;br /&gt;
== CAN-FD Support ==&lt;br /&gt;
The assignment editor now has support for CAN-FD.&lt;br /&gt;
&lt;br /&gt;
== Signal Reader New Type of Triggers are Introduced ==&lt;br /&gt;
A trigger in signal reader can now run the following events: Recorder (old), Setup switch (old), Pause diagnostics, Start/Stop CCP/XCP DAQ, Upload. Read more about triggers [[Signal Reader Assignment Editor|here]].&lt;br /&gt;
&lt;br /&gt;
== Improved Resource Groups Table under the Administration Tab ==&lt;br /&gt;
Resource group table has been extended with new columns that control if Require approved assignments and shows the number of resources and labels. It is also possible to filter on strict and nonstrict and a counter has been added in the header.&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WICE_Internal_Signals&amp;diff=3414</id>
		<title>WICE Internal Signals</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WICE_Internal_Signals&amp;diff=3414"/>
		<updated>2023-08-24T08:15:03Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The following WICE-internal signals are supported by Signal Reader:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&#039;&#039;&#039;Signal name&#039;&#039;&#039;&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|Accelerometer_X&lt;br /&gt;
|The value of the X direction of the WCU&#039;s built-in accelerometer. (See [[WICE Accelerometer]].) &lt;br /&gt;
|-&lt;br /&gt;
|Accelerometer_Y&lt;br /&gt;
|The value of the Y direction of the WCU&#039;s built-in accelerometer. (See [[WICE Accelerometer]].) &lt;br /&gt;
|-&lt;br /&gt;
|Accelerometer_Z&lt;br /&gt;
|The value of the Z direction of the WCU&#039;s built-in accelerometer. (See [[WICE Accelerometer]].) &lt;br /&gt;
|-&lt;br /&gt;
|Audio_Device_1&lt;br /&gt;
|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. &lt;br /&gt;
|-&lt;br /&gt;
|Audio_Device_2&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|Busload_CAN_&amp;lt;n&amp;gt;&lt;br /&gt;
|The bus load on CAN bus &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Connectivity&lt;br /&gt;
|The current connectivity of the WCU (0 = unknown, 1 = none, 2 = 2G, 3 = 3G, 4 = 4G, 5=5G, 6=WiFi, 7=ethernet) &lt;br /&gt;
|-&lt;br /&gt;
|CSQ&lt;br /&gt;
|The built-in modem&#039;s CSQ value (Signal Quality)&lt;br /&gt;
|-&lt;br /&gt;
|Date_Year&lt;br /&gt;
|The year of the current date. &lt;br /&gt;
|-&lt;br /&gt;
|Date_Month&lt;br /&gt;
|The month (1-12) of the current date. &lt;br /&gt;
|-&lt;br /&gt;
|Date_Day&lt;br /&gt;
|The day of the month (1-31) of the current date. &lt;br /&gt;
|-&lt;br /&gt;
|Date_Weekday&lt;br /&gt;
|The day of the week (1-7, where 1 is Sunday). &lt;br /&gt;
|-&lt;br /&gt;
|Date_Hour&lt;br /&gt;
|The hour of the day (0-23). &lt;br /&gt;
|-&lt;br /&gt;
|Date_Minute&lt;br /&gt;
|The minute of the hour (0-59). &lt;br /&gt;
|-&lt;br /&gt;
|Date_Second&lt;br /&gt;
|The second of the minute (0-59). &lt;br /&gt;
|-&lt;br /&gt;
|Dynamic_&amp;lt;n&amp;gt;&lt;br /&gt;
|Special signals with values assignable from external software components (typically used for Rapid Prototyping).&lt;br /&gt;
|-&lt;br /&gt;
|IO__AI_&amp;lt;n&amp;gt;&lt;br /&gt;
|Analog input number &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|IO__DI_&amp;lt;n&amp;gt;&lt;br /&gt;
|Digital input number &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|IO__DO_&amp;lt;n&amp;gt;&lt;br /&gt;
|Digital output number &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Log_All_Frames_CAN_&amp;lt;n&amp;gt;&lt;br /&gt;
|Log all CAN frames on CAN bus &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Log_All_Frames_FlexRay_&amp;lt;n&amp;gt;&lt;br /&gt;
|Log all CAN frames on Flexray bus &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Latitude&lt;br /&gt;
|The GPS latitude&lt;br /&gt;
|-&lt;br /&gt;
|Longitude&lt;br /&gt;
|The GPS longitude&lt;br /&gt;
|-&lt;br /&gt;
|Network_Receive_Rate_eth0&lt;br /&gt;
|The rate i kilobilts per second of receiving data on the eth0 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Receive_Rate_eth1&lt;br /&gt;
|The rate i kilobilts per second of receiving data on the eth1 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Receive_Rate_ppp0&lt;br /&gt;
|The rate i kilobilts per second of receiving data on the ppp0 (i.e. mobile data communication) interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Transmit_Rate_eth0&lt;br /&gt;
|The rate i kilobilts per second of transmitting data on the eth0 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Transmit_Rate_eth1&lt;br /&gt;
|The rate i kilobilts per second of transmitting data on the eth1 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Transmit_Rate_ppp0&lt;br /&gt;
|The rate i kilobilts per second of transmitting data on the ppp0 (i.e. mobile data communication)  interface &lt;br /&gt;
|-&lt;br /&gt;
|Power_Mode&lt;br /&gt;
|The power mode of the WCU&lt;br /&gt;
|-&lt;br /&gt;
|Random&lt;br /&gt;
|A random number generator&lt;br /&gt;
|-&lt;br /&gt;
|Random_Start&lt;br /&gt;
|A random number generator updated once, at program start&lt;br /&gt;
|-&lt;br /&gt;
|Random_Setup_Switch&lt;br /&gt;
|A random number generator updated at each measurement set-up switch&lt;br /&gt;
|-&lt;br /&gt;
|Start_Signal&lt;br /&gt;
|The start signal of the WCU &lt;br /&gt;
|-&lt;br /&gt;
|Start_Signal_Voltage&lt;br /&gt;
|The voltage of the start signal of the WCU, in millivolts &lt;br /&gt;
|-&lt;br /&gt;
|Speed&lt;br /&gt;
|The GPS speed&lt;br /&gt;
|-&lt;br /&gt;
|Start_Switch&lt;br /&gt;
|The start switch of the WCU&lt;br /&gt;
|-&lt;br /&gt;
|Tester_Present&lt;br /&gt;
|When present in a measurement set-up, a Tester Present diagnostic request (with suppress Positive Response bit set) will be sent periodically.  &lt;br /&gt;
|-&lt;br /&gt;
|Time_Since_Epoch&lt;br /&gt;
|The time elapsed since the epoch (Jan 1, 1970, 00:00) &lt;br /&gt;
|-&lt;br /&gt;
|Time_Since_Start&lt;br /&gt;
|The time elapsed since the start of the task &lt;br /&gt;
|-&lt;br /&gt;
|Time_Since_Setup_Switch&lt;br /&gt;
|The time elapsed since the activation of the current measurement set-up &lt;br /&gt;
|-&lt;br /&gt;
|Trigger_Button&lt;br /&gt;
|The trigger button connected to the WCU &lt;br /&gt;
|-&lt;br /&gt;
|Usage_CPU&lt;br /&gt;
|The WCU CPU usage in percent  &lt;br /&gt;
|-&lt;br /&gt;
|Usage_Memory&lt;br /&gt;
|The WCU memory usage in percent  &lt;br /&gt;
|-&lt;br /&gt;
|Video_Camera_1&lt;br /&gt;
|The status of video camera 1 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.  &lt;br /&gt;
|-&lt;br /&gt;
|Video_Camera_2&lt;br /&gt;
|The status of video camera 2 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.  &lt;br /&gt;
|-&lt;br /&gt;
|WCU_Battery&lt;br /&gt;
|The WCU battery voltage in millivolts&lt;br /&gt;
|-&lt;br /&gt;
|WCU_Temp&lt;br /&gt;
|The WCU internal temperature in degrees Celsius&lt;br /&gt;
|-&lt;br /&gt;
|WCU_Storage&lt;br /&gt;
|The available storage on the WCU in percent&lt;br /&gt;
|-&lt;br /&gt;
|WCU_Voltage&lt;br /&gt;
|The WCU voltage in millivolts&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WICE_Accelerometer&amp;diff=3413</id>
		<title>WICE Accelerometer</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WICE_Accelerometer&amp;diff=3413"/>
		<updated>2023-08-24T08:13:06Z</updated>

		<summary type="html">&lt;p&gt;Mathias: Created page with &amp;quot;The WICE-internal signals for the built-in accelerometer, WICE.Accelerometer_X, WICE.Accelerometer_X and WICE.Accelerometer_Z are oriented as in the below picture.  Orientation of the axes of the built-in accelerometer&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The WICE-internal signals for the built-in accelerometer, WICE.Accelerometer_X, WICE.Accelerometer_X and WICE.Accelerometer_Z are oriented as in the below picture. &lt;br /&gt;
[[File:WICE Accelerometer.png|thumb|Orientation of the axes of the built-in accelerometer]]&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=File:WICE_Accelerometer.png&amp;diff=3412</id>
		<title>File:WICE Accelerometer.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=File:WICE_Accelerometer.png&amp;diff=3412"/>
		<updated>2023-08-24T08:12:14Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Orientation of the axes of the built-in accelerometer&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WICE_RP_How-To&amp;diff=3411</id>
		<title>WICE RP How-To</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WICE_RP_How-To&amp;diff=3411"/>
		<updated>2023-08-21T12:11:47Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Getting Started with WICE Rapid Prototyping = &lt;br /&gt;
To get started developing an RP component to be run on a WICE WCU you need the following:&lt;br /&gt;
* A toolchain for building executable programs on the target WCU platform&lt;br /&gt;
* A set of libraries providing APIs to the WCU hardware platform resources (e.g. CAN, diagnostics, logging, etc)&lt;br /&gt;
* A high-level, socket based, Signal Broker API simplifying access to in-vehicle signals.&lt;br /&gt;
* WICE Portal access to configure the RP module for one or more WCUs&lt;br /&gt;
&lt;br /&gt;
== Software Development Toolchain ==&lt;br /&gt;
The development toolchain is typically installed on a desktop Linux system and then executables are built by cross-compilation.&lt;br /&gt;
The following WCU platform architectures are supported:&lt;br /&gt;
* Host Mobility MX-4: ARM Cortex A9 or Cortex A5 processor, 32 bit&lt;br /&gt;
* Fältcom Committo: ARM 926EJ-S processor, 32 bit &lt;br /&gt;
* Actia Platform: MIPS processor, 32 bit&lt;br /&gt;
&lt;br /&gt;
All toolchains are gcc-based.&lt;br /&gt;
The MX-4 toolchain is availble here: https://www.alkit.se/pub/gcc-linaro-arm-linux-gnueabihf-2012.09-20120921_linux.tar.gz&lt;br /&gt;
&lt;br /&gt;
== WICE RP development API libraries ==&lt;br /&gt;
The following libraries are available:&lt;br /&gt;
* Canwrapper CAN library&lt;br /&gt;
* Debug logging library&lt;br /&gt;
* Timers and utilities library&lt;br /&gt;
* Tactalib Diagnostics library&lt;br /&gt;
* OBD II library&lt;br /&gt;
&lt;br /&gt;
The development libraries are available here: https://www.alkit.se/rp/libs/&lt;br /&gt;
&lt;br /&gt;
Note that you do not need these libraries when using the high-level Signal Broker API (the preferred approach), described below.&lt;br /&gt;
&lt;br /&gt;
= Building and executing the RP program =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The binary file resulting from compiling the program for the target WCU platform is transferred to one or more in-vehicle WCUs using the WICE Portal. The binary will be executed&lt;br /&gt;
when the WCU boots, and will be terminated when the WCU shuts down.&lt;br /&gt;
&lt;br /&gt;
When executed, an number of command line arguments are given to the RP binary, as follows:&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
-vin &amp;lt;VIN number&amp;gt; -settings &amp;lt;filename&amp;gt; -logfile &amp;lt;filename&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;-vin&amp;lt;/code&amp;gt; parameter supplies the Vehicle Identification Number of the vehicle the WCU is installed in.&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;-settings&amp;lt;/code&amp;gt; parameter supplies the path to a configuration file the user can supply through the WICE portal.&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;-logfile&amp;lt;/code&amp;gt; parameter supplies the path to a debug log file which will be uploaded to WICE portal when the RP module exits.&lt;br /&gt;
&lt;br /&gt;
To get access to the information supplied on the command line at start-up, the RP program must parse the command line.&lt;br /&gt;
&lt;br /&gt;
= A simple example RP program =&lt;br /&gt;
The example code &amp;lt;code&amp;gt;rpex.c&amp;lt;/code&amp;gt; illustrates how to write a small program that can be executed as an RP module on the WICE in-vehicle WCU platform. &lt;br /&gt;
&lt;br /&gt;
The example shows how to read a configuration file supplied on the command line, to write a CAN diagnostic request on a CAN bus and read a diagnostic reply, and to log data to a log file that will be uploaded to the WICE Portal.&lt;br /&gt;
&lt;br /&gt;
The full source code of rpex is available [https://www.alkit.se/rp/example/ here].&lt;br /&gt;
&lt;br /&gt;
The first thing the example program does is to parse the command line parameters:&lt;br /&gt;
 &amp;lt;code&amp;gt;ret = parse_options(argc, argv);&lt;br /&gt;
  if (ret != 1) {&lt;br /&gt;
    return EXIT_FAILURE;&lt;br /&gt;
  }&amp;lt;/code&amp;gt;&lt;br /&gt;
The &amp;lt;code&amp;gt;parse_options&amp;lt;/code&amp;gt; function sets the variables &amp;lt;code&amp;gt;settings_filename&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;log_filename&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;vin&amp;lt;/code&amp;gt; to the strings supplied on the command line.&lt;br /&gt;
&lt;br /&gt;
Next, debug output is enabled, and the output filename is set to &amp;lt;code&amp;gt;log_filename&amp;lt;/code&amp;gt;, as specified on the command line. This ensures that the log file will be uploaded to the WICE Portal when rpex exits.&lt;br /&gt;
The &amp;lt;code&amp;gt;debug_enable&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;debug_msg&amp;lt;/code&amp;gt; functions are defined in the &amp;lt;code&amp;gt;alkit-debug&amp;lt;/code&amp;gt; development library.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;code&amp;gt;if (log_filename != NULL ) {&lt;br /&gt;
    debug_enable(log_filename);&lt;br /&gt;
 }&lt;br /&gt;
 debug_msg(1, &amp;quot;rpex version is %s\n&amp;quot;, RPEX_VERSION_STRING);&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, after some more log output, the settings file is read:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;code&amp;gt; if(settings_filename)&lt;br /&gt;
    read_settings(settings_filename);&amp;lt;/code&amp;gt;&lt;br /&gt;
The settings file is the main way (except for the command line parameters) to provide input to the RP program. It can contain any type of input data needed by the program. In the example, rpex only reads text from the settings file and prints it to the output logfile.&lt;br /&gt;
&lt;br /&gt;
The program is now ready to do its main work,in this case to send a diagnostic request on a CAN bus, and read a response. This is done using the &amp;lt;code&amp;gt;alkit-canwrapper&amp;lt;/code&amp;gt; library.&lt;br /&gt;
The following code block shows how to set up the CAN interface, prepare a CAN frame for transmission, set up a CAN filter matching the expected response, and then send the CAN frame.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;code&amp;gt; // Initialize CAN interface&lt;br /&gt;
  ret = init_can(canbus, DEFAULT_CAN_DEVICE);&lt;br /&gt;
  can_device_fd = get_can_fd(canbus);&lt;br /&gt;
  &amp;lt;br&amp;gt;&lt;br /&gt;
  // Set up CAN filter&lt;br /&gt;
  install_CAN_filter(canbus, 0, CAN_FILTER_TYPE_PASS, can_filter_id, can_filter_mask);&lt;br /&gt;
  &amp;lt;br&amp;gt;&lt;br /&gt;
  // Prepare CAN frame for request&lt;br /&gt;
  memset(&amp;amp;req_frame, 0, sizeof(candata_t));&lt;br /&gt;
  req_frame.id = ecu_id;&lt;br /&gt;
  req_frame.bus_nr = canbus;&lt;br /&gt;
  req_frame.frame_type = CAN_FRAME_11_BIT;&lt;br /&gt;
  memset(req_frame.databytes, 0, 8);&lt;br /&gt;
  req_frame.databytes[0] = 0x02; // SingleFrame, length = 2&lt;br /&gt;
  req_frame.databytes[1] = 0x10; // Service 10&lt;br /&gt;
  req_frame.databytes[2] = 0x01; // Default Diagnostic Session&lt;br /&gt;
  req_frame.databyte_count = 8; // With padding&lt;br /&gt;
  &amp;lt;br&amp;gt;&lt;br /&gt;
  // Send CAN frame&lt;br /&gt;
  debug_msg(1, &amp;quot;Sending diagnostic request on CAN bus %d...\n&amp;quot;, canbus);&lt;br /&gt;
  n = write_can(canbus, &amp;amp;req_frame, &amp;amp;t);&lt;br /&gt;
  if(n&amp;lt;0) {&lt;br /&gt;
    debug_msg(1, &amp;quot;Error writing CAN frame\n&amp;quot;);&lt;br /&gt;
    return -1;&lt;br /&gt;
  }&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following code block shows how to read a response CAN frame.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;code&amp;gt;// Read CAN response&lt;br /&gt;
  FD_ZERO(&amp;amp;readfds);&lt;br /&gt;
  FD_SET(can_device_fd, &amp;amp;readfds);&lt;br /&gt;
  timeout.tv_sec = 0;&lt;br /&gt;
  timeout.tv_usec = 200000; // 200 ms&lt;br /&gt;
  &amp;lt;br&amp;gt;&lt;br /&gt;
  ready = select(FD_SETSIZE, &amp;amp;readfds, NULL, NULL, &amp;amp;timeout);&lt;br /&gt;
  if (ready &amp;gt; 0) {&lt;br /&gt;
    ret = read_can(canbus, &amp;amp;resp_frame);&lt;br /&gt;
    if (ret == CAN_STATUS_OK) {&lt;br /&gt;
      // Read successful&lt;br /&gt;
      handle_can_frame(&amp;amp;resp_frame);&lt;br /&gt;
    } else {&lt;br /&gt;
      debug_msg(1, &amp;quot;Error reading CAN frame\n&amp;quot;);&lt;br /&gt;
    }&lt;br /&gt;
  } else {&lt;br /&gt;
    debug_msg(1, &amp;quot;No response.\n&amp;quot;);&lt;br /&gt;
  }&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The function &amp;lt;code&amp;gt;handle_can_frame&amp;lt;/code&amp;gt;which is called when a frame is read simply logs the CAN identifier and payload to the logfile.&lt;br /&gt;
&lt;br /&gt;
= Using the high-level API for reading in-vehicle signals =&lt;br /&gt;
To avoid the intricacies of reading CAN or FlexRay signals directly from the device, having to parse and interpret the signals, there is a high-level socket based API for reading in-vehicle and WICE-internal signals. The API is based on a publish/subscribe model, wherein the RP client subscribes to signals by name, and periodically gets signal values for the selected set of signals. The communication between the RP client and the WICE signal broker component is done over a socket.&lt;br /&gt;
&lt;br /&gt;
The example code &amp;lt;code&amp;gt;rpex-pubsub.c&amp;lt;/code&amp;gt; illustrates how to use the publish/subscribe API. The full source code is available [https://www.alkit.se/rp/example/ here].&lt;br /&gt;
&lt;br /&gt;
To set up the communication between the RP module and the signal broker, the example program calls a function called &amp;lt;code&amp;gt;setup_pubsub_connection()&amp;lt;/code&amp;gt; after parsing the command line parameters:&lt;br /&gt;
 &amp;lt;code&amp;gt;pubsub_socket = setup_pubsub_connection(ip_addr, port_num);&lt;br /&gt;
  if(pubsub_socket&amp;lt;0) {&lt;br /&gt;
    debug_msg(1, &amp;quot;Pubsub connection failed\n&amp;quot;);&lt;br /&gt;
    exit(-1);&lt;br /&gt;
  }&amp;lt;/code&amp;gt;&lt;br /&gt;
The &amp;lt;code&amp;gt;setup_pubsub_connection()&amp;lt;/code&amp;gt; function sets up a TCP socket to use for the communication.&lt;br /&gt;
&lt;br /&gt;
To this socket, a subscribe command is sent with a list of names of the signals to subscribe to. The syntax of the subscribe command is as follows:&lt;br /&gt;
 &amp;lt;code&amp;gt;subscribe &amp;lt;signal name 1&amp;gt; &amp;lt;signal name 2&amp;gt; ...&amp;lt;signal name n&amp;gt;&amp;lt;CRLF&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the separator character has to be space, and the line terminated with Carriage Return + Line Feed (or optionally only Line Feed).&lt;br /&gt;
 &amp;lt;code&amp;gt;sprintf(str, &amp;quot;subscribe %s %s\n&amp;quot;, RPEX_SIGNAL1, RPEX_SIGNAL2);&lt;br /&gt;
  n = send(pubsub_socket, str, strlen(str), 0);&lt;br /&gt;
  if(n &amp;lt;= 0) {&lt;br /&gt;
    debug_msg(1, &amp;quot;Error subscribing to signals\n&amp;quot;);&lt;br /&gt;
    exit(-1);&lt;br /&gt;
  }&lt;br /&gt;
 &amp;lt;/code&amp;gt;&lt;br /&gt;
Once the signals have been subscribed, the signal broker will send the signal values on the socket, to be read by the RP program, with the following syntax:&lt;br /&gt;
 &amp;lt;code&amp;gt;&amp;lt;signal name&amp;gt; &amp;lt;value&amp;gt;&amp;lt;CRLF&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
Again, the separator character between signal name and value is space.&lt;br /&gt;
&lt;br /&gt;
The following code segment show an example of how to read signals as the bcome available on the socket using the &amp;lt;code&amp;gt;select()&amp;lt;/code&amp;gt; system call.&lt;br /&gt;
 &amp;lt;code&amp;gt;while(count &amp;lt; 100) {&lt;br /&gt;
    FD_ZERO(&amp;amp;readfds);&lt;br /&gt;
    FD_SET(pubsub_socket, &amp;amp;readfds);&lt;br /&gt;
    timeout.tv_sec = 1;&lt;br /&gt;
    timeout.tv_usec = 0;&lt;br /&gt;
    ready = select(FD_SETSIZE, &amp;amp;readfds, NULL, NULL, &amp;amp;timeout);&lt;br /&gt;
    if (ready &amp;gt; 0) {&lt;br /&gt;
      n = read_line(pubsub_socket, &amp;amp;buf);&lt;br /&gt;
      if (n &amp;gt; 0) {&lt;br /&gt;
        // Read successful&lt;br /&gt;
        handle_signal(buf);&lt;br /&gt;
        free(buf);&lt;br /&gt;
        count++;&lt;br /&gt;
      } else {&lt;br /&gt;
        debug_msg(1, &amp;quot;Error reading signal\n&amp;quot;);&lt;br /&gt;
        break;&lt;br /&gt;
      }&lt;br /&gt;
    }&lt;br /&gt;
  }&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;read_line()&amp;lt;/code&amp;gt; helper function handles the actual reading of characters from the socket, and then the &amp;lt;code&amp;gt;handle_signal()&amp;lt;/code&amp;gt; function parses the signal names and values, as follows. &lt;br /&gt;
 &amp;lt;code&amp;gt;void handle_signal(char *str) {&lt;br /&gt;
  char name[1000];&lt;br /&gt;
  float value;&lt;br /&gt;
  sscanf(str, &amp;quot;%s %f&amp;quot;, name, &amp;amp;value);&lt;br /&gt;
  if(strcmp(name, RPEX_SIGNAL1)==0)&lt;br /&gt;
    debug_msg(1, &amp;quot;The value of signal 1 is %f\n&amp;quot;, value);&lt;br /&gt;
  if(strcmp(name, RPEX_SIGNAL2)==0)&lt;br /&gt;
    debug_msg(1, &amp;quot;The value of signal 2 is %f\n&amp;quot;, value);&lt;br /&gt;
 }&amp;lt;/code&amp;gt;&lt;br /&gt;
The RP program can at any time unsubscribe to signals using the &amp;lt;code&amp;gt;unsubscribe&amp;lt;/code&amp;gt; command, which has the same syntax as the &amp;lt;code&amp;gt;subscribe&amp;lt;/code&amp;gt; command.&lt;br /&gt;
 &amp;lt;code&amp;gt;unsubscribe &amp;lt;signal name 1&amp;gt; &amp;lt;signal name 2&amp;gt; ...&amp;lt;signal name n&amp;gt;&amp;lt;CRLF&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
After unsubscribing to a (subset) of the subscribed signals, those signals&#039; values will no longer be transmitted on the socket. (This is not shown in the example.)&lt;br /&gt;
&lt;br /&gt;
The final part of the example shows how to terminate the subscription using the &amp;lt;code&amp;gt;quit&amp;lt;/code&amp;gt; command.&lt;br /&gt;
 &amp;lt;code&amp;gt;send(pubsub_socket, &amp;quot;quit&amp;quot;, 4, 0);&lt;br /&gt;
  close(pubsub_socket);&amp;lt;/code&amp;gt;&lt;br /&gt;
As another example, the following Python code illustrates how to set up a socket connection th the Signal Broker, list the available signals, and subscribe to them.&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 # Example showing how to read signals from WICE Signal Broker in Python&lt;br /&gt;
 &lt;br /&gt;
 import socket&lt;br /&gt;
 &lt;br /&gt;
 HOST = &amp;quot;127.0.0.1&amp;quot;&lt;br /&gt;
 PORT = 31415&lt;br /&gt;
 &lt;br /&gt;
 def read_line(sock):&lt;br /&gt;
    &amp;quot;read a line from a socket&amp;quot;&lt;br /&gt;
    chars = []&lt;br /&gt;
    while True:&lt;br /&gt;
        a = sock.recv(1)&lt;br /&gt;
        chars.append(a)     &lt;br /&gt;
        if a == &amp;quot;\n&amp;quot; or a == &amp;quot;&amp;quot;:&lt;br /&gt;
            return &amp;quot;&amp;quot;.join(chars)&lt;br /&gt;
 &lt;br /&gt;
 def read_signals(sock):&lt;br /&gt;
    &amp;quot;read available signals&amp;quot;&lt;br /&gt;
    sigs = []&lt;br /&gt;
    while True:&lt;br /&gt;
        line = read_line(sock)&lt;br /&gt;
        if line == &amp;quot;\n&amp;quot; or line == &amp;quot;\r\n&amp;quot; or line == &amp;quot;&amp;quot;:&lt;br /&gt;
            return sigs&lt;br /&gt;
        sigs.append(dict(name = line.strip(), value = 0.0))&lt;br /&gt;
 &lt;br /&gt;
 def parse_signal(str):&lt;br /&gt;
    &amp;quot;parse  string into signal name tuple&amp;quot;&lt;br /&gt;
    x = str.split()&lt;br /&gt;
    t = (x[0], x[1])&lt;br /&gt;
    return t&lt;br /&gt;
 &lt;br /&gt;
 print(&amp;quot;Setting up socket connection to port %d...&amp;quot; % PORT)&lt;br /&gt;
 sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)&lt;br /&gt;
 sock.connect((HOST, PORT))&lt;br /&gt;
 # Get list of available signals&lt;br /&gt;
 sock.send(&amp;quot;list\n&amp;quot;)&lt;br /&gt;
 signals = read_signals(sock)&lt;br /&gt;
 &lt;br /&gt;
 print(&amp;quot;Available signals:&amp;quot;)&lt;br /&gt;
 print(signals)&lt;br /&gt;
 &lt;br /&gt;
 # Subscribe to signals&lt;br /&gt;
 for signal in signals:&lt;br /&gt;
    sock.send(&amp;quot;subscribe &amp;quot; + signal[&amp;quot;name&amp;quot;] + &amp;quot;\n&amp;quot;)&lt;br /&gt;
  &lt;br /&gt;
 while True:&lt;br /&gt;
    line = read_line(sock)&lt;br /&gt;
    t = parse_signal(line)&lt;br /&gt;
    for s in signals:&lt;br /&gt;
        if s[&amp;quot;name&amp;quot;] == t[0]:&lt;br /&gt;
            s.update({&amp;quot;value&amp;quot;: t[1]})&lt;br /&gt;
            break&lt;br /&gt;
    print(&amp;quot;Signal &amp;quot; + s[&amp;quot;name&amp;quot;] + &amp;quot;, value = &amp;quot; + str(s[&amp;quot;value&amp;quot;]))&lt;br /&gt;
 s.close()&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
You can find more information about the signal broker API in [[WICE Signal Broker API]] section.&lt;br /&gt;
&lt;br /&gt;
= Rapid Prototyping using Node.js =&lt;br /&gt;
To develop Rapid Prototyping applications with graphical user interfaces, the [https://nodejs.org Node.js] framework can be used. Node.js is a cross-platform JavaScript run-time environment that executes JavaScript code on the server side. In the WICE RP concept, a Node.js application can be downloaded to a WCU where it is executed. The user interface developed can be accessed from a web browser connected to the WCU through Ethernet or WiFi. The setup described here is built with Node.js Express. However, other frameworks can be utilized using the same methodology, with small modifications. &lt;br /&gt;
&lt;br /&gt;
All written to consol.log() will be in a log-file called rp-webapp-&amp;lt;date&amp;gt;.log and uploaded and accessible in the WICE back end. &lt;br /&gt;
&lt;br /&gt;
The following example demonstrates how to access vehicle signals from a Node.js application running on a WCU.&lt;br /&gt;
&lt;br /&gt;
In the Node.js application server set-up script, add the following code segment to include the Express framework and &amp;lt;code&amp;gt;socket.io&amp;lt;/code&amp;gt; handling socket communication.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;code&amp;gt;// Setup server environment&lt;br /&gt;
 const express = require(&#039;express&#039;);&lt;br /&gt;
 const app = express();&lt;br /&gt;
 const server = require(&#039;http&#039;).createServer(app);&lt;br /&gt;
 const io = require(&#039;socket.io&#039;)(server);&lt;br /&gt;
 &lt;br /&gt;
 // Run internal util&lt;br /&gt;
 require(&#039;/path/to/script/socketHandler.js&#039;)(io)&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;code&amp;gt;socketHandler.js&amp;lt;/code&amp;gt; script contains the code that handles the socket communication, both with the web-client and with the WICE Signal Broker. The function waits for a client to connect, by accessing the web page. It then connects to the Signal Broker and subscribes to the desired signals (in this example Engine Speed and Vehicle Speed on the MS CAN bus). The application then listens for incoming messages on the connected socket and processes the data, i.e. signal names and values. The data is then transferred to the client by &amp;lt;code&amp;gt;socket.io&amp;lt;/code&amp;gt; communication in order to present the information in the web-browser. An example &amp;lt;code&amp;gt;socketHandler.js&amp;lt;/code&amp;gt; script is outlined here:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;code&amp;gt;const net = require(&#039;net&#039;);&lt;br /&gt;
 const PORT = 31415;&lt;br /&gt;
 &lt;br /&gt;
 module.exports = function(io) {      &lt;br /&gt;
   io.on(&#039;connection&#039;, function(client) {  // Await client connection&lt;br /&gt;
       console.log(&#039;Client connected...&#039;);&lt;br /&gt;
 &lt;br /&gt;
       // Setup TCP socket to Signal Broker.&lt;br /&gt;
       var tcpSocket = new net.Socket();&lt;br /&gt;
       tcpSocket.connect(PORT, &#039;localhost&#039;, function () {&lt;br /&gt;
           console.log(&#039;Connected to signal broker... &#039;);&lt;br /&gt;
 &lt;br /&gt;
           // Get a list of available signals (optional)&lt;br /&gt;
           tcpSocket.write(&#039;list\n&#039;); &lt;br /&gt;
 		&lt;br /&gt;
           // Subscribe to desired signals. &lt;br /&gt;
           tcpSocket.write(&#039;subscribe CAN_MS.EngineSpeed CAN_MS.VehicleSpeed\n&#039;);&lt;br /&gt;
       });&lt;br /&gt;
 	&lt;br /&gt;
      // Listener triggered by messages from sigread.      &lt;br /&gt;
     tcpSocket.on(&#039;data&#039;, function(message) {       &lt;br /&gt;
        console.log(message.toString());  &lt;br /&gt;
        // Handle received messages here...&lt;br /&gt;
     });&lt;br /&gt;
 &lt;br /&gt;
     // Triggered if the tcpSocket is closed.&lt;br /&gt;
     tcpSocket.on(&#039;close&#039;, function () {&lt;br /&gt;
           console.log(&#039;TCP connection closed!&#039;);&lt;br /&gt;
      });&lt;br /&gt;
 &lt;br /&gt;
     // Triggered upon error events.&lt;br /&gt;
     tcpSocket.on(&#039;error&#039;, function(error) {&lt;br /&gt;
           console.log(&#039;TCP error: %s&#039;, error);&lt;br /&gt;
      });&lt;br /&gt;
 &lt;br /&gt;
     // Triggered if the client refreshes or closes the page&lt;br /&gt;
      client.on(&#039;disconnect&#039;, function (){&lt;br /&gt;
           console.log(&amp;quot;Client disconnected&amp;quot;);  &lt;br /&gt;
           tcpSocket.destroy(); // Disconnect from Signal Broker&lt;br /&gt;
      });&lt;br /&gt;
   });  &lt;br /&gt;
 }&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Each received message is a newline-terminated text line consisting of signal name followed by signal value, separated by a space character (see [[#Using the high-level API for reading in-vehicle signals|Signal Broker]] section above). The message is transferred to the client through socket communication established in the first part of the script above.&lt;br /&gt;
&lt;br /&gt;
Send data to client:&lt;br /&gt;
 &amp;lt;code&amp;gt;client.emit(&#039;speed&#039;, speed);&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Receive data in HTML-embedded client script:&lt;br /&gt;
 &amp;lt;code&amp;gt;// Setup client socket.&lt;br /&gt;
 var socket = io.connect(&#039;/&#039;); // url path for the current page&lt;br /&gt;
 socket.on(&#039;connect&#039;, function (data) {&lt;br /&gt;
      console.log(&amp;quot;Client connected to server&amp;quot;);&lt;br /&gt;
 });&lt;br /&gt;
 	&lt;br /&gt;
 // Triggered by ‘speed’ tagged messages from server.&lt;br /&gt;
 socket.on(&#039;speed&#039;, function (value) {&lt;br /&gt;
               console.log(value);&lt;br /&gt;
 });&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To transfer a Node web-app to one or more WCUs, it should be put in a zip file and uploaded to the WICE Portal as an RP module.&lt;br /&gt;
The zip file must have a top level directory called &amp;lt;code&amp;gt;rp&amp;lt;/code&amp;gt;, and in this directory a Node application entry point file called &amp;lt;code&amp;gt;server.js&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
A complete example of a Node web-application RP zip-file, including source code, is available for download [https://www.alkit.se/rp/node-example/ here].&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.84&amp;diff=3400</id>
		<title>New features in v2.84</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.84&amp;diff=3400"/>
		<updated>2023-06-29T07:38:52Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* WCU information panel extended with certificate expire date */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Context menu added for some plot options in the signal preview ==&lt;br /&gt;
A context menu has been added in the signal preview when right clicking the plot. The menu gives you the opportunity to toggle the visibility of the chart title, the y-axes titles and the y-axes themselves. It also gives you the option to toggle between having the file name or signal names as the plot title.&lt;br /&gt;
== Improved tooltip when hovering over the plot ==&lt;br /&gt;
The tooltip that appears when you hover over the plot in the signal preview now showcase the value of all signals and just not the one closest to the cursor.&lt;br /&gt;
== Functionality added to add more files to plot without loosing signal selection ==&lt;br /&gt;
When viewing signals in the signal preview you can now add more files without loosing the settings or the selections of your current plot. This is done by pressing the new &amp;quot;Add more files&amp;quot; button which takes you back where you can add new files in and also remove old files.&lt;br /&gt;
== Show/hide module button of signal preview improved ==&lt;br /&gt;
The show/hide module button in the signal preview now applies the module names to the signal list and the signal preview instead of only effecting the signal list.&lt;br /&gt;
== Allow more signals in signal preview ==&lt;br /&gt;
The maximum number of signals in a plot is now infinitely many signals in a single plot.&lt;br /&gt;
== WCU information panel extended with certificate expiry date ==&lt;br /&gt;
The WCU information panel now also shows the certificates expiry date. Hovering over the date will also show how many days left before the certificate expires.&lt;br /&gt;
&lt;br /&gt;
== Support to have per-vehicle ECU PIN codes ==&lt;br /&gt;
For SWDL tasks there is now support to have ECU PIN codes per vehicle instead of just global ones for a task. See further in [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|ECU PIN codes for vehicles]] on how to prepare a vehicle with individual pin codes and on creating SWDL tasks [[Creating a Task#SWDL|here]].&lt;br /&gt;
&lt;br /&gt;
== New Canrecorder ==&lt;br /&gt;
A new Canrecorder is introduced in 2.84 with design changes and some new settings like: trigger option and shot count. Read more [[Creating a Task#CAN-recorder|here.]]&lt;br /&gt;
&lt;br /&gt;
== New WICE-internal signals in Signal Reader ==&lt;br /&gt;
Two new WICE-internal signals are introduced in introduced in 2.84: WICE.WCU_Storage, giving the available storage on the WCU in percent, and WICE.Connectivity, giving the current connectivity mode. Read more [[WICE_Internal_Signals|here.]]&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.84&amp;diff=3399</id>
		<title>New features in v2.84</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.84&amp;diff=3399"/>
		<updated>2023-06-29T07:38:10Z</updated>

		<summary type="html">&lt;p&gt;Mathias: /* Support to have per vehicle ECU pin codes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Context menu added for some plot options in the signal preview ==&lt;br /&gt;
A context menu has been added in the signal preview when right clicking the plot. The menu gives you the opportunity to toggle the visibility of the chart title, the y-axes titles and the y-axes themselves. It also gives you the option to toggle between having the file name or signal names as the plot title.&lt;br /&gt;
== Improved tooltip when hovering over the plot ==&lt;br /&gt;
The tooltip that appears when you hover over the plot in the signal preview now showcase the value of all signals and just not the one closest to the cursor.&lt;br /&gt;
== Functionality added to add more files to plot without loosing signal selection ==&lt;br /&gt;
When viewing signals in the signal preview you can now add more files without loosing the settings or the selections of your current plot. This is done by pressing the new &amp;quot;Add more files&amp;quot; button which takes you back where you can add new files in and also remove old files.&lt;br /&gt;
== Show/hide module button of signal preview improved ==&lt;br /&gt;
The show/hide module button in the signal preview now applies the module names to the signal list and the signal preview instead of only effecting the signal list.&lt;br /&gt;
== Allow more signals in signal preview ==&lt;br /&gt;
The maximum number of signals in a plot is now infinitely many signals in a single plot.&lt;br /&gt;
== WCU information panel extended with certificate expire date ==&lt;br /&gt;
The WCU information panel now also shows the certificates expiry date. Hovering over the date will also show how many days left before the certificate expires.&lt;br /&gt;
&lt;br /&gt;
== Support to have per-vehicle ECU PIN codes ==&lt;br /&gt;
For SWDL tasks there is now support to have ECU PIN codes per vehicle instead of just global ones for a task. See further in [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|ECU PIN codes for vehicles]] on how to prepare a vehicle with individual pin codes and on creating SWDL tasks [[Creating a Task#SWDL|here]].&lt;br /&gt;
&lt;br /&gt;
== New Canrecorder ==&lt;br /&gt;
A new Canrecorder is introduced in 2.84 with design changes and some new settings like: trigger option and shot count. Read more [[Creating a Task#CAN-recorder|here.]]&lt;br /&gt;
&lt;br /&gt;
== New WICE-internal signals in Signal Reader ==&lt;br /&gt;
Two new WICE-internal signals are introduced in introduced in 2.84: WICE.WCU_Storage, giving the available storage on the WCU in percent, and WICE.Connectivity, giving the current connectivity mode. Read more [[WICE_Internal_Signals|here.]]&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.84&amp;diff=3398</id>
		<title>New features in v2.84</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=New_features_in_v2.84&amp;diff=3398"/>
		<updated>2023-06-29T07:37:26Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Context menu added for some plot options in the signal preview ==&lt;br /&gt;
A context menu has been added in the signal preview when right clicking the plot. The menu gives you the opportunity to toggle the visibility of the chart title, the y-axes titles and the y-axes themselves. It also gives you the option to toggle between having the file name or signal names as the plot title.&lt;br /&gt;
== Improved tooltip when hovering over the plot ==&lt;br /&gt;
The tooltip that appears when you hover over the plot in the signal preview now showcase the value of all signals and just not the one closest to the cursor.&lt;br /&gt;
== Functionality added to add more files to plot without loosing signal selection ==&lt;br /&gt;
When viewing signals in the signal preview you can now add more files without loosing the settings or the selections of your current plot. This is done by pressing the new &amp;quot;Add more files&amp;quot; button which takes you back where you can add new files in and also remove old files.&lt;br /&gt;
== Show/hide module button of signal preview improved ==&lt;br /&gt;
The show/hide module button in the signal preview now applies the module names to the signal list and the signal preview instead of only effecting the signal list.&lt;br /&gt;
== Allow more signals in signal preview ==&lt;br /&gt;
The maximum number of signals in a plot is now infinitely many signals in a single plot.&lt;br /&gt;
== WCU information panel extended with certificate expire date ==&lt;br /&gt;
The WCU information panel now also shows the certificates expiry date. Hovering over the date will also show how many days left before the certificate expires.&lt;br /&gt;
&lt;br /&gt;
== Support to have per vehicle ECU pin codes ==&lt;br /&gt;
For SWDL tasks there is now support to have ECU pin codes per vehicle instead of just global ones for a task. See further in [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|ECU pin codes for vehicles]] on how to prepare a vehicle with individual pin codes and on creating SWDL tasks [[Creating a Task#SWDL|here]].&lt;br /&gt;
&lt;br /&gt;
== New Canrecorder ==&lt;br /&gt;
A new Canrecorder is introduced in 2.84 with design changes and some new settings like: trigger option and shot count. Read more [[Creating a Task#CAN-recorder|here.]]&lt;br /&gt;
&lt;br /&gt;
== New WICE-internal signals in Signal Reader ==&lt;br /&gt;
Two new WICE-internal signals are introduced in introduced in 2.84: WICE.WCU_Storage, giving the available storage on the WCU in percent, and WICE.Connectivity, giving the current connectivity mode. Read more [[WICE_Internal_Signals|here.]]&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
	<entry>
		<id>https://wiki.alkit.se/wice299/index.php?title=WICE_Internal_Signals&amp;diff=3397</id>
		<title>WICE Internal Signals</title>
		<link rel="alternate" type="text/html" href="https://wiki.alkit.se/wice299/index.php?title=WICE_Internal_Signals&amp;diff=3397"/>
		<updated>2023-06-29T07:31:41Z</updated>

		<summary type="html">&lt;p&gt;Mathias: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
The following WICE-internal signals are supported by Signal Reader:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&#039;&#039;&#039;Signal name&#039;&#039;&#039;&lt;br /&gt;
!Description&lt;br /&gt;
|-&lt;br /&gt;
|Accelerometer_X&lt;br /&gt;
|The value of the X direction of the WCU&#039;s built-in accelerometer. &lt;br /&gt;
|-&lt;br /&gt;
|Accelerometer_Y&lt;br /&gt;
|The value of the Y direction of the WCU&#039;s built-in accelerometer. &lt;br /&gt;
|-&lt;br /&gt;
|Accelerometer_Z&lt;br /&gt;
|The value of the Z direction of the WCU&#039;s built-in accelerometer. &lt;br /&gt;
|-&lt;br /&gt;
|Audio_Device_1&lt;br /&gt;
|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. &lt;br /&gt;
|-&lt;br /&gt;
|Audio_Device_2&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|Busload_CAN_&amp;lt;n&amp;gt;&lt;br /&gt;
|The bus load on CAN bus &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Connectivity&lt;br /&gt;
|The current connectivity of the WCU (0 = unknown, 1 = none, 2 = 2G, 3 = 3G, 4 = 4G, 5=5G, 6=WiFi, 7=ethernet) &lt;br /&gt;
|-&lt;br /&gt;
|CSQ&lt;br /&gt;
|The built-in modem&#039;s CSQ value (Signal Quality)&lt;br /&gt;
|-&lt;br /&gt;
|Date_Year&lt;br /&gt;
|The year of the current date. &lt;br /&gt;
|-&lt;br /&gt;
|Date_Month&lt;br /&gt;
|The month (1-12) of the current date. &lt;br /&gt;
|-&lt;br /&gt;
|Date_Day&lt;br /&gt;
|The day of the month (1-31) of the current date. &lt;br /&gt;
|-&lt;br /&gt;
|Date_Weekday&lt;br /&gt;
|The day of the week (1-7, where 1 is Sunday). &lt;br /&gt;
|-&lt;br /&gt;
|Date_Hour&lt;br /&gt;
|The hour of the day (0-23). &lt;br /&gt;
|-&lt;br /&gt;
|Date_Minute&lt;br /&gt;
|The minute of the hour (0-59). &lt;br /&gt;
|-&lt;br /&gt;
|Date_Second&lt;br /&gt;
|The second of the minute (0-59). &lt;br /&gt;
|-&lt;br /&gt;
|Dynamic_&amp;lt;n&amp;gt;&lt;br /&gt;
|Special signals with values assignable from external software components (typically used for Rapid Prototyping).&lt;br /&gt;
|-&lt;br /&gt;
|IO__AI_&amp;lt;n&amp;gt;&lt;br /&gt;
|Analog input number &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|IO__DI_&amp;lt;n&amp;gt;&lt;br /&gt;
|Digital input number &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|IO__DO_&amp;lt;n&amp;gt;&lt;br /&gt;
|Digital output number &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Log_All_Frames_CAN_&amp;lt;n&amp;gt;&lt;br /&gt;
|Log all CAN frames on CAN bus &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Log_All_Frames_FlexRay_&amp;lt;n&amp;gt;&lt;br /&gt;
|Log all CAN frames on Flexray bus &amp;lt;n&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|Latitude&lt;br /&gt;
|The GPS latitude&lt;br /&gt;
|-&lt;br /&gt;
|Longitude&lt;br /&gt;
|The GPS longitude&lt;br /&gt;
|-&lt;br /&gt;
|Network_Receive_Rate_eth0&lt;br /&gt;
|The rate i kilobilts per second of receiving data on the eth0 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Receive_Rate_eth1&lt;br /&gt;
|The rate i kilobilts per second of receiving data on the eth1 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Receive_Rate_ppp0&lt;br /&gt;
|The rate i kilobilts per second of receiving data on the ppp0 (i.e. mobile data communication) interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Transmit_Rate_eth0&lt;br /&gt;
|The rate i kilobilts per second of transmitting data on the eth0 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Transmit_Rate_eth1&lt;br /&gt;
|The rate i kilobilts per second of transmitting data on the eth1 interface &lt;br /&gt;
|-&lt;br /&gt;
|Network_Transmit_Rate_ppp0&lt;br /&gt;
|The rate i kilobilts per second of transmitting data on the ppp0 (i.e. mobile data communication)  interface &lt;br /&gt;
|-&lt;br /&gt;
|Power_Mode&lt;br /&gt;
|The power mode of the WCU&lt;br /&gt;
|-&lt;br /&gt;
|Random&lt;br /&gt;
|A random number generator&lt;br /&gt;
|-&lt;br /&gt;
|Random_Start&lt;br /&gt;
|A random number generator updated once, at program start&lt;br /&gt;
|-&lt;br /&gt;
|Random_Setup_Switch&lt;br /&gt;
|A random number generator updated at each measurement set-up switch&lt;br /&gt;
|-&lt;br /&gt;
|Start_Signal&lt;br /&gt;
|The start signal of the WCU &lt;br /&gt;
|-&lt;br /&gt;
|Start_Signal_Voltage&lt;br /&gt;
|The voltage of the start signal of the WCU, in millivolts &lt;br /&gt;
|-&lt;br /&gt;
|Speed&lt;br /&gt;
|The GPS speed&lt;br /&gt;
|-&lt;br /&gt;
|Start_Switch&lt;br /&gt;
|The start switch of the WCU&lt;br /&gt;
|-&lt;br /&gt;
|Tester_Present&lt;br /&gt;
|When present in a measurement set-up, a Tester Present diagnostic request (with suppress Positive Response bit set) will be sent periodically.  &lt;br /&gt;
|-&lt;br /&gt;
|Time_Since_Epoch&lt;br /&gt;
|The time elapsed since the epoch (Jan 1, 1970, 00:00) &lt;br /&gt;
|-&lt;br /&gt;
|Time_Since_Start&lt;br /&gt;
|The time elapsed since the start of the task &lt;br /&gt;
|-&lt;br /&gt;
|Time_Since_Setup_Switch&lt;br /&gt;
|The time elapsed since the activation of the current measurement set-up &lt;br /&gt;
|-&lt;br /&gt;
|Trigger_Button&lt;br /&gt;
|The trigger button connected to the WCU &lt;br /&gt;
|-&lt;br /&gt;
|Usage_CPU&lt;br /&gt;
|The WCU CPU usage in percent  &lt;br /&gt;
|-&lt;br /&gt;
|Usage_Memory&lt;br /&gt;
|The WCU memory usage in percent  &lt;br /&gt;
|-&lt;br /&gt;
|Video_Camera_1&lt;br /&gt;
|The status of video camera 1 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.  &lt;br /&gt;
|-&lt;br /&gt;
|Video_Camera_2&lt;br /&gt;
|The status of video camera 2 (1=connected, 0 = disconnected). When present in a recorder, the video module will record video from the camera.  &lt;br /&gt;
|-&lt;br /&gt;
|WCU_Battery&lt;br /&gt;
|The WCU battery voltage in millivolts&lt;br /&gt;
|-&lt;br /&gt;
|WCU_Temp&lt;br /&gt;
|The WCU internal temperature in degrees Celsius&lt;br /&gt;
|-&lt;br /&gt;
|WCU_Storage&lt;br /&gt;
|The available storage on the WCU in percent&lt;br /&gt;
|-&lt;br /&gt;
|WCU_Voltage&lt;br /&gt;
|The WCU voltage in millivolts&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Mathias</name></author>
	</entry>
</feed>