https://wiki.alkit.se/wice297/api.php?action=feedcontributions&feedformat=atom&user=Robin.karhuWICE Wiki v2.97 - User contributions [en]2026-05-07T19:39:12ZUser contributionsMediaWiki 1.44.0https://wiki.alkit.se/wice297/index.php?title=File:Dlt-uds-task.png&diff=4170File:Dlt-uds-task.png2026-02-20T07:49:09Z<p>Robin.karhu: Robin.karhu uploaded a new version of File:Dlt-uds-task.png</p>
<hr />
<div>A view of the DLT UDS task.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Creating_a_Task&diff=4169Creating a Task2026-02-19T17:50:34Z<p>Robin.karhu: /* DLT UDS Mode */</p>
<hr />
<div><includeonly>== Creating a Task==</includeonly><br />
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of task you want to create. Note that it is not possible to create a new task for a WCU which has the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU has the latter label, it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of 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. <br />
<br />
To learn about how to add resources to the task, check [[New task|here]].<br />
<br />
== Arcos ==<br />
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]<br />
The WICE system can interact with external loggers as well. From version 2.71 the portal can interact with the Arcos-logger from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.ccmc''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.<br />
<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the Arcos - no upload will be required.<br />
<br />
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]]).<br />
<br />
== Area5 ==<br />
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]<br />
Area5 tasks are used to read out data from the memory of ECUs. <br />
<br />
'''Assignment:''' To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. <br />
<br />
'''Validate ECU SW version on WCU:''' By checking this box, the WCU will validate that the ECU SW version of the task and the actual ECU are the same before starting the task. If they are different, it will not start the task.<br />
<br />
'''Trigger Expression:''' The task can be started by an expression. This option lets the user specify start trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). For an explanation of trigger conditions look [[Server Trigger|here]].<br />
<br />
'''Sync Signal:''' It is possible to specify a signal with given values that will be sent when the Area5 task starts and stops. This can be used to synchronize the Area5 read-out with external measurements systems like the M-Log.<br />
<br />
== Audio ==<br />
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:<br />
* '''Trigger button''': to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.<br />
* '''Signal reader''': initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader '''recorder''' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the audio recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. <br />
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of triggers look [[Server Trigger|here]].<br />
* '''Audio level''': Start the trigger once the microphone registers volume above a certain threshold.<br />
* '''None''': start the recording as soon as possible.<br />
<br />
In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.<br />
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. <br />
<br />
There is more information about audio in WICE [[Wice audio|here]].<br />
<br />
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
== Blue piraT ==<br />
The blue PiraT is a measurement system from Telemotive AG that can be configured with measurement set-ups, and data accessed through the WICE Portal. Note that to use the blue PiraT module, the WCUs to be used need to be preconfigured with a special software package (i.e. an "extra bundle"). Contact Alkit Communications in order to set this up.<br />
<br />
== CAN-recorder ==<br />
[[File:Canrecorder.png|thumb|Canrecorder]]<br />
Canrecorder is a measurement module that allows CAN frames to be captured and logged.<br />
<br />
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.<br />
<br />
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”<br />
<br />
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. <br />
<br />
===Scheduling=== <br />
<br />
For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached. By selecting the "On ignition" checkbox, the task will be performed once on ignition. If delay is above 0 then the task will be performed once the configured amount of seconds have passed after ignition.<br />
<br />
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]<br />
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with 'On ignition' enabled]]<br />
<br clear="all"><br />
<br />
To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the [[The Portal Administrator View#The Vehicles Tab|Vehicles panel]]. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.<br />
<br />
== Diagnostic Log and Trace (DLT) ==<br />
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 "DLT UDS mode". <br />
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]<br />
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 "Enable multi task" checkbox as can be seen in the screenshot the right. <br />
<br />
=== DLT Daemon Mode ===<br />
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]. <br />
<br />
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. <br />
<br />
So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:<br />
<br />
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check "Use vehicle announcement" (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.<br />
# Daemon port - which port on the address the daemon is at.<br />
# 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].<br />
<br />
=== DLT UDS Mode ===<br />
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 "Add transfer". 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.<br />
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]<br />
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]].<br />
<br />
There is also a button "Check PINs" 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.<br />
<br />
== ETAS ==<br />
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.<br />
<br />
When creating an ETAS task, the task description file you select must be a .exp file.<br />
<br />
== Ethernet capture ==<br />
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]].<br />
<br />
== File fetcher ==<br />
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]<br />
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.<br />
<br />
The following needs to be specified when creating such a task:<br />
<br />
* '''File path''' - One or several paths to a files or file-containing directories on the unit's file system. This specifies which files that will be fetched.<br />
* '''Username''' - To log in to the unit.<br />
* '''Password''' - To log in to the unit.<br />
* '''IP address''' - To find the unit.<br />
* '''Port''' - To find the unit. Default is 22, but can be changed.<br />
<br />
Furthermore, the task also allows the use of a proxy.<br />
<br />
To use a proxy, the '''Use Proxy''' checkbox has to be checked, and the following must be specified:<br />
<br />
* '''Proxy Username''' - To log in to the proxy unit.<br />
* '''Proxy Password''' - To log in to the proxy unit.<br />
* '''Proxy IP Address''' - To find the proxy unit.<br />
* '''Proxy Port''' - To find the proxy unit. Default is 22, but can be changed.<br /><br />
== IDC ==<br />
The Internal Diagnostic Client (IDC) is a measurement module that allows a sequence of diagnostic requests to be sent and responses recorded. The sequence of diagnostic requests can be created as an assignment in the Assignment tab, alternatively can be uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
== IPEmotion RT ==<br />
The WICE system can interact with external loggers as well. From version 2.72 the portal can interact with the logger IPEmotion RT from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.irf''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.<br />
<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.<br />
<br />
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]]).<br />
<br />
== LPD ==<br />
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.<br />
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]<br />
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]<br />
From version 2.83.0 of the WICE portal the task measurement file can be updated via the View Task function in the Tasks tab and a dialog as shown to the right will appear. By pressing the "Edit" button in the lower right corner, you will be presented with the possibility to upload a new measurement task file. This is shown with a red triangle in the illustration on the right.<br />
<br />
== M-Log ==<br />
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]]<br />
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the MLOG - no upload will be required.<br />
<br />
==== Software version validation (Available from version 2.74.0) ====<br />
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. <br />
<br />
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 "Add" button. The data you just entered will be added to the table and evaluated against what the WICE system has read out from the vehicle. In the example to the right something is incorrect which is indicated by the yellow color. To see the exact reason, simply use the cursor to see the specific message. <br />
<br />
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 "Submit". <br />
<br />
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. <br />
<br />
== MQTT ==<br />
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.<br />
<br />
== Rapid prototyping ==<br />
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]].<br />
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]<br />
The rapid prototyping tab can be seen in Figure "Rapid prototyping task". <br />
<br />
An RP task must consist of at least an 'RP binary' or a 'Web application zip file'.<br />
<br />
== SoftHub ==<br />
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.<br />
<br />
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. <br />
<br />
The SoftHub task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''server triggers''' to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].<br />
<br />
== Signal Reader == <br />
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]<br />
Signal Reader is a data capture module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data, and ECU-internal signals read by CCP or XCP. To create a Signal Reader task you proceed as follows:<br />
<br />
1. You either select an assignment file of .haf format, or choose an assignment created in the assignment creator (see [[Signal Reader Assignment Wizard]]). Your current choice will be displayed in the "Chosen file" field.<br />
<br />
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]].<br />
<br />
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting "Monitor signals". When selected, two boxes will appear under the task description. In the left one you search for signals and drag them over to the right one where the signals to be monitored are listed. You can later see the monitored signals by pressing the '''Monitor Signals''' button either in the Tasks tab or in the Vehicles tab. It is also possible to copy the signals text in the bottom right corner of the right box. Next to the copy text button you can also paste signals as text where the pasted signal names will be matched against the list of unselected signals<br />
<br />
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).<br />
<br />
5. The Signal Reader task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''Server Triggers''' to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].<br />
<br />
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
=== The Signal Broker === <br />
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]].<br />
<br />
=== Files containing references to sequence files === <br />
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] <br />
If the measurement file contains references to sequence files, you are also required to select these in order to run the task. The portal scans the .haf file for such entries and presents this to you, see illustration 4.2. Click the button for each sequence file reference to upload each sequence file needed. Some requests in the sequence file may be for reading DTCs, and in such cases you can select the option of also reading associated ''Snapshots'' or ''Extended data''. An example of this can found in Figure "Sequence Files References in .haf File". <br />
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] <br />
<br />
Here, the .haf file contained two references to sequence files. As no sequence files have yet been uploaded, the selection for reading snapshot or extended data is grayed out. In Figure "Sequence File with Functional Query" we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read ''Extended data''. It is also possible to select both ''Snapshots'' and ''Extended data''. <br />
<br><br />
<br />
=== WICE internal signals ===<br />
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]]<br />
<br />
== SoH ==<br />
[[File:SoH.png|thumb|799x799px|SoH]]<br />
A State of Health (SoH) task collects specific status information from vehicles. You select which information you want the task to collect by filling in one or more of the checkboxes shown in Figure "SoH". The number of checkboxes shown can vary depending on the WICE installation. In order for SoH data to be correctly interpreted, relevant description files (e.g. SDDB) for the vehicles executing the SoH task may have to been available. To add such a description file for a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:<br />
*Mileage<br />
*Voltage<br />
*Read ECU software numbers<br />
*Read ECU DTC:s (optionally including 'Snapshot' and 'Extended data')<br />
*Read OBD-II PIDs<br />
*App Diagnotstic Db Part Num<br />
*Build ID<br />
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]<br />
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)<br />
*Clear DTCs. <br />
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)<br />
**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)<br />
*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 'engine_hours' (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle. <br />
<br />
This task can also be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
Some selections above might not be available to you as this is a configuration setting depending on customer.<br />
<br />
== SWDL ==<br />
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]<br />
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table. <br />
<br />
SWDL tasks can optionally include a '''pre-update sequence file and/or a post-update sequence file'''. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.<br />
<br />
SWDL tasks can optionally include one '''signature file''' (containing checksums). The file is assumed to be an xml file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)<br />
<br />
SWDL tasks can optionally include a '''VGM unlock''' access control mechanism, with a PIN code for the VGM node. This is specifically for vehicles requiring this kind of access control for ECU re-programming.<br />
<br />
By checking the box '''Run SoH after completion''' it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.<br />
<br />
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "'''Use Vehicle Pin mappings'''". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].<br />
<br />
SWDL tasks can optionally contain a '''Trigger Expression''' which must be fulfilled within a specified time limit ("Wait time") for ECU re-programming to be allowed. The trigger expression follows the same syntax as Signal Reader trigger expressions (or [[Server Trigger|Server Triggers]], audio/video triggers), and should be built up from signals being measured in a Signal Reader assignment. The user must make sure that there is a Signal Reader assignment on the WCUs of the SWDL task, with the signals of the trigger expression being measured.<br />
<br />
<br />
It is also possible to choose to '''ignore checksums''' and/or '''disable pre-programming''' using the corresponding checkboxes.<br />
<br />
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).<br />
<br />
== Video ==<br />
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:<br />
* '''Trigger button''': To initiate the recording you need to attach a button to the WCU in order to start in the video recording.<br />
* '''Signal reader''': Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader ''recorder'' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the video recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. <br />
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of how to enter triggers, have a look [[Server Trigger|here]].<br />
* '''None''': start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)<br />
<br />
In addition to this, you can set the '''pre-trig''' time (not valid in the cases of the 'None' trigger option above). As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the video has already been recorded for the number of seconds specified.<br />
<br />
A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.<br />
<br />
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.<br />
<br />
Read more about the video support in WICE [[WICE_video|here]].<br />
<br />
== Applicable for all types ==<br />
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]].<br />
<br />
=== Site specific features ===<br />
<br />
==== Announce result file availability ====<br />
[[File:Resultfilepanel.png|thumb|Announced On column]]<br />
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there's a new 'Announced On' column that keeps track of when the result file was announced.<br />
<br />
==== Retention time ====<br />
[[File:Retention time.png|thumb|435x435px|Retention time]]<br />
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. <br />
<br />
It is possible to set a default retention time for resource groups. To do this, add a global value label named '''RETENTION_TIME''' to the resource group and give it an appropriate value. This value will then be used as a template value when creating a new task for this resource group. If multiple resource groups have this label and they have different values, the one with the lowest/shortest retention time value will be chosen as the template value.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4168New features in v2.972026-02-19T17:37:33Z<p>Robin.karhu: /* Vehicle Communication Forwarder now uses SGA */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.<br />
<br />
== Vehicle Communication Forwarder now uses SGA ==<br />
[[Vehicle Communication Forwarder|Vehicle Communication Forwarder (VCF)]], or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab|via PIE]] or [[Vehicles#Upload Vehicle pins|from file]].<br />
<br />
In addition to checking if there is a PIN available via the Check PINs button mentioned [[New features in v2.97#Show whether PINs are available for a vehicle|above]], an icon will indicate whether an appropriate PIN is available on the WCUs vehicle.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.<br />
<br />
== Raw MRCOM mode for Vehicle Communication Forwarder ==<br />
[[File:MRCOM forwarding mode.png|thumb|MRCOM forwarding]]<br />
[[File:Raw MRCOM.png|thumb|Raw MRCOM]]<br />
In addition to standard MRCOM forwarding via SGA, a [[Vehicle Communication Forwarder|VCF]] can now be configured to instead use raw MRCOM via ethernet.<br />
<br />
When raw MRCOM mode is selected, it is then possible to choose whether to use ETH0 or ETH1 as ethernet interface. Since SGA is not used for raw MRCOM, uploading a PIN for SGA is not necessary.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4167New features in v2.972026-02-19T17:34:16Z<p>Robin.karhu: /* Vehicle Communication Forwarder now uses SGA */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.<br />
<br />
== Vehicle Communication Forwarder now uses SGA ==<br />
Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab|via PIE]] or [[Vehicles#Upload Vehicle pins|from file]].<br />
<br />
In addition to checking if there is a PIN available via the Check PINs button mentioned [[New features in v2.97#Show whether PINs are available for a vehicle|above]], an icon will indicate whether an appropriate PIN is available on the WCUs vehicle.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.<br />
<br />
== Raw MRCOM mode for Vehicle Communication Forwarder ==<br />
[[File:MRCOM forwarding mode.png|thumb|MRCOM forwarding]]<br />
[[File:Raw MRCOM.png|thumb|Raw MRCOM]]<br />
In addition to standard MRCOM forwarding via SGA, a VCF can now be configured to instead use raw MRCOM via ethernet.<br />
<br />
When raw MRCOM mode is selected, it is then possible to choose whether to use ETH0 or ETH1 as ethernet interface. Since SGA is not used for raw MRCOM, uploading a PIN for SGA is not necessary.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4166New features in v2.972026-02-19T17:33:41Z<p>Robin.karhu: /* Vehicle Communication Forwarder now uses SGA */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.<br />
<br />
== Vehicle Communication Forwarder now uses SGA ==<br />
Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab|via PIE]] or [[Vehicles#Upload Vehicle pins|from file]].<br />
<br />
In addition to checking if there is a PIN available for SGA on area 0x17 via the Check PINs button mentioned [[New features in v2.97#Show whether PINs are available for a vehicle|above]], an icon will indicate whether an appropriate PIN is available on the WCUs vehicle.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.<br />
<br />
== Raw MRCOM mode for Vehicle Communication Forwarder ==<br />
[[File:MRCOM forwarding mode.png|thumb|MRCOM forwarding]]<br />
[[File:Raw MRCOM.png|thumb|Raw MRCOM]]<br />
In addition to standard MRCOM forwarding via SGA, a VCF can now be configured to instead use raw MRCOM via ethernet.<br />
<br />
When raw MRCOM mode is selected, it is then possible to choose whether to use ETH0 or ETH1 as ethernet interface. Since SGA is not used for raw MRCOM, uploading a PIN for SGA is not necessary.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicle_Communication_Forwarder&diff=4165Vehicle Communication Forwarder2026-02-19T16:41:58Z<p>Robin.karhu: </p>
<hr />
<div>A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.<br />
<br />
It is also possible to configure LIN channels on the VCF, with the same requirements.<br />
<br />
Due to now using SGA instead of HIA and HIB, requires WCU version 2.97.0 or higher (previously required 2.89.0).<br />
<br />
To read more about adding a VCF, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.<br />
<br />
A PIN for SGA area 0x17 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu|individual]] or for [[Vehicles#Upload Vehicle pins|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.<br />
[[File:VCF MRCOM forwarding.png|thumb|768x768px|VCF MRCOM forwarding with CAN and LIN channel configurations]]<br />
[[File:VCF raw MRCOM.png|thumb|769x769px|VCF raw MRCOM with CAN and LIN channel configurations]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:VCF_raw_MRCOM.png&diff=4164File:VCF raw MRCOM.png2026-02-19T16:40:33Z<p>Robin.karhu: </p>
<hr />
<div>Raw MRCOM mode selected. ETH0 is the chosen ethernet interface.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:VCF_MRCOM_forwarding.png&diff=4163File:VCF MRCOM forwarding.png2026-02-19T16:39:14Z<p>Robin.karhu: </p>
<hr />
<div>MRCOM forwarding mode selected. Has valid SGA PIN.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicle_Communication_Forwarder&diff=4162Vehicle Communication Forwarder2026-02-19T16:37:04Z<p>Robin.karhu: </p>
<hr />
<div>A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.<br />
<br />
It is also possible to configure LIN channels on the VCF, with the same requirements.<br />
<br />
Due to now using SGA instead of HIA and HIB, requires WCU version 2.97.0 or higher (previously required 2.89.0).<br />
<br />
To read more about adding a VCF, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.<br />
<br />
A PIN for SGA area 0x17 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu|individual]] or for [[Vehicles#Upload Vehicle pins|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.<br />
[[File:VCF LIN - 2.91.0.png|thumb|768x768px|CAN and LIN channel configurations]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=I/O_configurations&diff=4161I/O configurations2026-02-19T16:34:08Z<p>Robin.karhu: check PINs</p>
<hr />
<div><div class="keywords"> io, io configurations, io config, io configs </div><br />
<includeonly>= I/O configurations =</includeonly><br />
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".<br />
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]<br />
<br />
==Edit CAN channels==<br />
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]<br />
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.<br />
<br />
===Channel===<br />
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.<br />
<br />
===Speed (kB)===<br />
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.<br />
<br />
=== FD Speed (kB) ===<br />
[[File:Wcu-configuration-can-fd.png|alt=CAN FD setting for the HMX platform|thumb|CAN FD setting for the HMX platform]]<br />
If the platform is HMX and the WCU version is 2.91.0 or later, a column will appear for the CAN channel. <br />
<br />
===Name===<br />
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.<br />
<br />
===Comment===<br />
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.<br />
<br />
===Add WMU(s)===<br />
If your Portal has [[WMU | WMU's]] enabled the "Add WMU" button will show in the CAN section. You can then add/remove WMU's and configure their CAN channels in the same way as the WCU's CAN channels are configured. For each WMU that is added, a corresponding tab is added under the [[The_Portal_Administrator_View#WMU's_Power_Management | Power Management tab]] for configuring the WMU's power behaviour.<br />
<br />
=== Add CAN channels ===<br />
If your Portal has Vehicle Communication Forwarder enabled, the "Add CAN channels" button will show in the CAN section. If both WMUs and Vehicle Communication Forwarder are enabled in your Portal, only "Add CAN channels" will show up. After having added a Vehicle Communication Forwarder with at least one CAN channel, pressing the button again will add more CAN channels to the Vehicle Communication Forwarder. When removing CAN channels, it is possible to either remove the entire Vehicle Communication Forwarder, or individual CAN channels from it.<br />
<br />
==Edit Ethernet Channels==<br />
[[File:NewEthernetChannel.png|thumb|Edit Ethernet Channels]]<br />
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains eight columns and the individual meaning is as follows.<br />
<br />
===Channel===<br />
This column indicates which interface or interfaces that exists.<br />
<br />
===Addressing mode===<br />
In this column the Addressing mode is configured. The choices are "DHCP client", "AutoIP" and "Static".<br />
<br />
===IP address===<br />
Here you set the static IP address if you have selected "Static" as the Addressing mode.<br />
<br />
===Netmask===<br />
Here you set the netmask if you have selected "Static" as the Addressing mode.<br />
<br />
===Default route===<br />
Here you set the default route if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. The default route is the route that takes effect when no other route is available for an IP destination address.<br />
<br />
===Name Server (DNS)===<br />
Here you set the Name Server if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. Here you set the name of the DNS protocol.<br />
<br />
===Name===<br />
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.<br />
<br />
===Comment===<br />
In this column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.<br />
<br />
=== Role (Automotive only) ===<br />
[[File:EthernetChannelWithAutomotive.png|thumb|Ethernet Channel With Automotive]]<br />
Here you can select a role between Master and Slave. this is only available from version 2.97.0 and later.<br />
<br />
=== Speed (Automotive only) ===<br />
In this field, the user can select the speed (in Mbps) for the Ethernet channel. The available options are 100 Mbps and 1000 Mbps. This feature is available starting from version 2.97.0.<br />
<br />
==The Miscellaneous Section==<br />
[[File:Screenshot from 2024-09-16 09-49-47.png|thumb|Miscellaneous]]<br />
This section is available for WCUs with version 2.49 or later.<br />
===Set digital out 3 on boot=== <br />
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).<br />
<br />
===Diagnostic tester priority===<br />
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".<br />
<br />
=== Allow ethernet activation on WCU ===<br />
For WCUs of version 2.90.4 or later it is possible to choose whether or not to allow the WCU to use ethernet activation. Not allowing this might disturb some of the WCUs features.<br />
<br />
===Set 5V out on boot===<br />
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.<br />
<br />
===Activate buzzer on detected digital input change===<br />
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.<br />
<br />
=== Diagnostic firewall disable and PIN ===<br />
Option to disable diagnostic firewall. Requires PIN. Visible for WCUs with version 2.89.0 or later.<br />
<br />
=== Diagnostic tester detection ===<br />
Option to detect any diagnostic testers that they may not be interrupted, typically during OTA. Available for WCUs with version 2.96.0 or later.<br />
<br />
==Manage templates==<br />
[[File:Io config2.png|thumb|frame|Selecting Template]]<br />
Admins can save configs as templates (see [[#Manage templates (for admins) | Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.<br />
Clicking "Apply" will apply the selected template. You can always change settings or add more info, the template could be anything you need or just act as a starting point.<br />
<br />
If WMUs are enabled in the portal, a template will save the CANs from each WMU and when a template is selected the WMU CANs are applied 1:1 to each existing WMU in the configuration. <br />
If there are no WMUs in the configuration the template's WMU CANs will not be applied, only the WCU's CANs.<br />
<br />
==Manage templates (for admins)==<br />
[[File:Io config3.png|thumb|frame|Manage Templates (admin view)]]<br />
[[File:Io config4.png|thumb|frame|Manage Templates (with WMUs enabled)]]<br />
If you are an admin you have an extra button "Save current config as template" in the Manage configuration templates window. Clicking it to save the current configuration as a template will prompt you for a name. If the name already exists (case insensitive) a confirmation dialog will popup before overwriting.<br />
<br />
Additionally, as admin you will be able to remove existing templates, which is done by clicking the red "Remove record" icon to the right of the template name. A confirmation dialog will popup to prevent deletion by mistake.<br />
<br />
==Show Vehicle Profile==<br />
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]<br />
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.<br />
<br />
== Check PINs ==<br />
Requires version 2.97.0 or later and that checking PINs is enabled for the portal. Pressing "Check PINs" will open a new window that displays which ECUs have PINs and and for which areas.<br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). PINs can also be fetched from PIE via ''Administration''->''Resource group''s. Read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]], and about uploading PINs from file [[Vehicles#Upload Vehicle pins|here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=I/O_configurations&diff=4160I/O configurations2026-02-19T16:32:54Z<p>Robin.karhu: /* Apply uploaded PINs */</p>
<hr />
<div><div class="keywords"> io, io configurations, io config, io configs </div><br />
<includeonly>= I/O configurations =</includeonly><br />
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".<br />
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]<br />
<br />
==Edit CAN channels==<br />
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]<br />
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.<br />
<br />
===Channel===<br />
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.<br />
<br />
===Speed (kB)===<br />
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.<br />
<br />
=== FD Speed (kB) ===<br />
[[File:Wcu-configuration-can-fd.png|alt=CAN FD setting for the HMX platform|thumb|CAN FD setting for the HMX platform]]<br />
If the platform is HMX and the WCU version is 2.91.0 or later, a column will appear for the CAN channel. <br />
<br />
===Name===<br />
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.<br />
<br />
===Comment===<br />
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.<br />
<br />
===Add WMU(s)===<br />
If your Portal has [[WMU | WMU's]] enabled the "Add WMU" button will show in the CAN section. You can then add/remove WMU's and configure their CAN channels in the same way as the WCU's CAN channels are configured. For each WMU that is added, a corresponding tab is added under the [[The_Portal_Administrator_View#WMU's_Power_Management | Power Management tab]] for configuring the WMU's power behaviour.<br />
<br />
=== Add CAN channels ===<br />
If your Portal has Vehicle Communication Forwarder enabled, the "Add CAN channels" button will show in the CAN section. If both WMUs and Vehicle Communication Forwarder are enabled in your Portal, only "Add CAN channels" will show up. After having added a Vehicle Communication Forwarder with at least one CAN channel, pressing the button again will add more CAN channels to the Vehicle Communication Forwarder. When removing CAN channels, it is possible to either remove the entire Vehicle Communication Forwarder, or individual CAN channels from it.<br />
<br />
==Edit Ethernet Channels==<br />
[[File:NewEthernetChannel.png|thumb|Edit Ethernet Channels]]<br />
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains eight columns and the individual meaning is as follows.<br />
<br />
===Channel===<br />
This column indicates which interface or interfaces that exists.<br />
<br />
===Addressing mode===<br />
In this column the Addressing mode is configured. The choices are "DHCP client", "AutoIP" and "Static".<br />
<br />
===IP address===<br />
Here you set the static IP address if you have selected "Static" as the Addressing mode.<br />
<br />
===Netmask===<br />
Here you set the netmask if you have selected "Static" as the Addressing mode.<br />
<br />
===Default route===<br />
Here you set the default route if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. The default route is the route that takes effect when no other route is available for an IP destination address.<br />
<br />
===Name Server (DNS)===<br />
Here you set the Name Server if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. Here you set the name of the DNS protocol.<br />
<br />
===Name===<br />
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.<br />
<br />
===Comment===<br />
In this column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.<br />
<br />
=== Role (Automotive only) ===<br />
[[File:EthernetChannelWithAutomotive.png|thumb|Ethernet Channel With Automotive]]<br />
Here you can select a role between Master and Slave. this is only available from version 2.97.0 and later.<br />
<br />
=== Speed (Automotive only) ===<br />
In this field, the user can select the speed (in Mbps) for the Ethernet channel. The available options are 100 Mbps and 1000 Mbps. This feature is available starting from version 2.97.0.<br />
<br />
==The Miscellaneous Section==<br />
[[File:Screenshot from 2024-09-16 09-49-47.png|thumb|Miscellaneous]]<br />
This section is available for WCUs with version 2.49 or later.<br />
===Set digital out 3 on boot=== <br />
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).<br />
<br />
===Diagnostic tester priority===<br />
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".<br />
<br />
=== Allow ethernet activation on WCU ===<br />
For WCUs of version 2.90.4 or later it is possible to choose whether or not to allow the WCU to use ethernet activation. Not allowing this might disturb some of the WCUs features.<br />
<br />
===Set 5V out on boot===<br />
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.<br />
<br />
===Activate buzzer on detected digital input change===<br />
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.<br />
<br />
=== Diagnostic firewall disable and PIN ===<br />
Option to disable diagnostic firewall. Requires PIN. Visible for WCUs with version 2.89.0 or later.<br />
<br />
=== Diagnostic tester detection ===<br />
Option to detect any diagnostic testers that they may not be interrupted, typically during OTA. Available for WCUs with version 2.96.0 or later.<br />
<br />
==Manage templates==<br />
[[File:Io config2.png|thumb|frame|Selecting Template]]<br />
Admins can save configs as templates (see [[#Manage templates (for admins) | Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.<br />
Clicking "Apply" will apply the selected template. You can always change settings or add more info, the template could be anything you need or just act as a starting point.<br />
<br />
If WMUs are enabled in the portal, a template will save the CANs from each WMU and when a template is selected the WMU CANs are applied 1:1 to each existing WMU in the configuration. <br />
If there are no WMUs in the configuration the template's WMU CANs will not be applied, only the WCU's CANs.<br />
<br />
==Manage templates (for admins)==<br />
[[File:Io config3.png|thumb|frame|Manage Templates (admin view)]]<br />
[[File:Io config4.png|thumb|frame|Manage Templates (with WMUs enabled)]]<br />
If you are an admin you have an extra button "Save current config as template" in the Manage configuration templates window. Clicking it to save the current configuration as a template will prompt you for a name. If the name already exists (case insensitive) a confirmation dialog will popup before overwriting.<br />
<br />
Additionally, as admin you will be able to remove existing templates, which is done by clicking the red "Remove record" icon to the right of the template name. A confirmation dialog will popup to prevent deletion by mistake.<br />
<br />
==Show Vehicle Profile==<br />
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]<br />
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.<br />
<br />
== Check PINs ==<br />
Requires version 2.97.0 or later and that checking PINs is enabled for the portal. Pressing "Check PINs" will open a new window that displays which ECUs have PINs and and for which areas.<br />
<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). PINs can also be fetched from PIE via ''Administration''->''Resource group''s. Read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]], and about uploading PINs from file [[Vehicles#Upload Vehicle pins|here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicle_Communication_Forwarder&diff=4159Vehicle Communication Forwarder2026-02-19T16:24:40Z<p>Robin.karhu: SGA instead of HIA & HIB</p>
<hr />
<div>A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.<br />
<br />
It is also possible to configure LIN channels on the VCF, with the same requirements.<br />
<br />
Due to now using SGA instead of HIA and HIB, requires WCU version 2.97.0 or higher (previously required 2.89.0).<br />
<br />
To read more about adding a VCF, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.<br />
<br />
A PIN for SGA area 0x17 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu|individual]] or for [[Vehicles#Upload Vehicle pins|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.<br />
[[File:Vehicle Communications Forwarder CAN channels.png|thumb|CAN channel configuration|769x769px]]<br />
[[File:VCF LIN - 2.91.0.png|thumb|768x768px|CAN and LIN channel configurations]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4158New features in v2.972026-02-19T16:07:47Z<p>Robin.karhu: /* Raw MRCOM mode for Vehicle Communication Forwarder */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.<br />
<br />
== Vehicle Communication Forwarder now uses SGA ==<br />
Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and PINs must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab|via PIE]] or [[Vehicles#Upload Vehicle pins|from file]].<br />
<br />
In addition to checking if there is a PIN available for SGA on area 0x17 via the Check PINs button mentioned [[New features in v2.97#Show whether PINs are available for a vehicle|above]], an icon will indicate whether an appropriate PIN is available on the WCUs vehicle.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.<br />
<br />
== Raw MRCOM mode for Vehicle Communication Forwarder ==<br />
[[File:MRCOM forwarding mode.png|thumb|MRCOM forwarding]]<br />
[[File:Raw MRCOM.png|thumb|Raw MRCOM]]<br />
In addition to standard MRCOM forwarding via SGA, a VCF can now be configured to instead use raw MRCOM via ethernet.<br />
<br />
When raw MRCOM mode is selected, it is then possible to choose whether to use ETH0 or ETH1 as ethernet interface. Since SGA is not used for raw MRCOM, uploading a PIN for SGA is not necessary.<br />
<br />
Only available if Vehicle Communication Forwarder is enabled for the portal.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4157New features in v2.972026-02-19T16:04:58Z<p>Robin.karhu: VCF SGA and raw MRCOM</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.<br />
<br />
== Vehicle Communication Forwarder now uses SGA ==<br />
Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and PINs must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab|via PIE]] or [[Vehicles#Upload Vehicle pins|from file]].<br />
<br />
In addition to checking if there is a PIN available for SGA on area 0x17 via the Check PINs button mentioned [[New features in v2.97#Show whether PINs are available for a vehicle|above]], an icon will indicate whether an appropriate PIN is available on the WCUs vehicle.<br />
<br />
== Raw MRCOM mode for Vehicle Communication Forwarder ==<br />
[[File:MRCOM forwarding mode.png|thumb|MRCOM forwarding]]<br />
[[File:Raw MRCOM.png|thumb|Raw MRCOM]]<br />
In addition to standard MRCOM forwarding via SGA, a VCF can now be configured to instead use raw MRCOM via ethernet.<br />
<br />
When raw MRCOM mode is selected, it is then possible to choose whether to use ETH0 or ETH1 as ethernet interface. Since SGA is not used for raw MRCOM, uploading a PIN for SGA is not necessary.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:Raw_MRCOM.png&diff=4156File:Raw MRCOM.png2026-02-19T16:02:35Z<p>Robin.karhu: </p>
<hr />
<div>Raw MRCOM selected. Can choose ETH0 or ETH1 as ethernet interface.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:MRCOM_forwarding_mode.png&diff=4155File:MRCOM forwarding mode.png2026-02-19T16:01:08Z<p>Robin.karhu: </p>
<hr />
<div>MRCOM forwarding selected. Shows if PIN is available for SGA.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4154New features in v2.972026-02-19T15:30:44Z<p>Robin.karhu: /* Show whether PINs are available for a vehicle */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
[[File:Check PINs result.png|thumb|Check PINs result]]<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:Check_PINs_result.png&diff=4153File:Check PINs result.png2026-02-19T15:24:30Z<p>Robin.karhu: </p>
<hr />
<div>Shows which ECUs and for which areas there are PINs available for the vehicle.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4152New features in v2.972026-02-19T15:21:44Z<p>Robin.karhu: /* Show whether PINs are available for a vehicle */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4151New features in v2.972026-02-19T15:19:43Z<p>Robin.karhu: /* Show whether PINs are available for a vehicle */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle. <br />
<br />
Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4150New features in v2.972026-02-19T15:16:41Z<p>Robin.karhu: check PINs</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].<br />
<br />
== Show whether PINs are available for a vehicle ==<br />
If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4149New features in v2.972026-02-19T14:53:39Z<p>Robin.karhu: /* Removed manual entry of pin codes for DLT tasks */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. This will then use the supplied ECU and area to determine which PIN is to be used. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4148New features in v2.972026-02-19T14:50:46Z<p>Robin.karhu: /* Changes to DLT tasks */</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.<br />
<br />
To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)|click here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.97&diff=4147New features in v2.972026-02-19T14:48:41Z<p>Robin.karhu: DLT</p>
<hr />
<div>== Add all signals and multiple signal sources for signal reader in the assignment editor. ==<br />
It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.<br />
<br />
An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.<br />
<br />
A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.<br />
<br />
== Support for WCU hardened mode. ==<br />
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.”<br />
<br />
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.<br />
<br />
== Support for automatically generating passwords ==<br />
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]].<br />
<br />
== Additional settings for ethernet interfaces on HMX for automotive Ethernet ==<br />
Starting with version 2.97.0, the Ethernet interface settings on HMX have been extended with two additional fields for automotive Ethernet: '''Role''' and '''Speed'''. For automotive Ethernet channels, only the '''Static''' addressing mode is supported. Read more about it [[I/O configurations#Role (Automotive only)|here]].<br />
<br />
== Configurable default time interval for alarms in portal ==<br />
It is now possible to set a default alarm interval directly in the portal. Users can do this by right-clicking the '''Active Alarms''' column in the '''Vehicles''' tab or by navigating to the '''Alarms''' tab in '''Administration''' and clicking the '''Set Alarm Interval''' button. Read more [[Alarm#Set Alarm Interval|here]].<br />
<br />
== Improvements to Creating/View Mapping on Signal Reader Task ==<br />
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]<br />
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]<br />
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. <br />
<br />
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 'Signal Reader Create Mapping'." To read more about this, [[Mappings|click here]].<br />
<br />
== Improved timestamping in Signal Reader ==<br />
The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.<br />
<br />
== Changes to DLT tasks ==<br />
<br />
==== Edit DLT tasks ====<br />
It is now possible to edit running DLT tasks. For UDS service 38 it is possible to edit ECU, service area code, and directory. For DLT daemons it is possible to edit the address, port and configuration, as well as whether to use vehicle announcement instead of address.<br />
<br />
==== Enable scheduling for DLT tasks ====<br />
Scheduling is now possible for all new DLT tasks.<br />
<br />
==== Removed manual entry of pin codes for DLT tasks ====<br />
It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|uploading PINs from file]] prior to creating the task. Checking whether PINs are available/missing for a given ECU and area can also be done directly from the DLT UDS task.<br />
<br />
==== Selectable area code for DLT tasks ====<br />
It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.96&diff=4097New features in v2.962025-11-06T15:18:42Z<p>Robin.karhu: </p>
<hr />
<div>This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.<br />
<br />
== DLT Daemon mode and DLT UDS in parallel ==<br />
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).]]<br />
<br />
== DLT Daemon address via vehicle announcement ==<br />
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).]]<br />
<br />
== Set, View, and Apply Default WCU Configurations ==<br />
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]].<br />
<br />
== Users can now shelve a WCU directly from the Vehicles panel ==<br />
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]].<br />
<br />
== VINReader option to not request VIN if known ==<br />
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.<br />
<br />
== Support for diagnostic Build ID request ==<br />
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.<br />
<br />
== Diagnostic tester detection ==<br />
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the [[I/O configurations#The Miscellaneous Section|IO tab]] when editing the configuration.<br />
<br />
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==<br />
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.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=I/O_configurations&diff=4096I/O configurations2025-11-06T15:17:04Z<p>Robin.karhu: /* The Miscellaneous Section */</p>
<hr />
<div><div class="keywords"> io, io configurations, io config, io configs </div><br />
<includeonly>= I/O configurations =</includeonly><br />
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".<br />
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]<br />
<br />
==Edit CAN channels==<br />
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]<br />
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.<br />
<br />
===Channel===<br />
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.<br />
<br />
===Speed (kB)===<br />
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.<br />
<br />
=== FD Speed (kB) ===<br />
[[File:Wcu-configuration-can-fd.png|alt=CAN FD setting for the HMX platform|thumb|CAN FD setting for the HMX platform]]<br />
If the platform is HMX and the WCU version is 2.91.0 or later, a column will appear for the CAN channel. <br />
<br />
===Name===<br />
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.<br />
<br />
===Comment===<br />
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.<br />
<br />
===Add WMU(s)===<br />
If your Portal has [[WMU | WMU's]] enabled the "Add WMU" button will show in the CAN section. You can then add/remove WMU's and configure their CAN channels in the same way as the WCU's CAN channels are configured. For each WMU that is added, a corresponding tab is added under the [[The_Portal_Administrator_View#WMU's_Power_Management | Power Management tab]] for configuring the WMU's power behaviour.<br />
<br />
=== Add CAN channels ===<br />
If your Portal has Vehicle Communication Forwarder enabled, the "Add CAN channels" button will show in the CAN section. If both WMUs and Vehicle Communication Forwarder are enabled in your Portal, only "Add CAN channels" will show up. After having added a Vehicle Communication Forwarder with at least one CAN channel, pressing the button again will add more CAN channels to the Vehicle Communication Forwarder. When removing CAN channels, it is possible to either remove the entire Vehicle Communication Forwarder, or individual CAN channels from it.<br />
<br />
==Edit Ethernet Channels==<br />
[[File:NewEthernetChannel.png|thumb|Edit Ethernet Channels]]<br />
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains eight columns and the individual meaning is as follows.<br />
<br />
===Channel===<br />
This column indicates which interface or interfaces that exists.<br />
<br />
===Addressing mode===<br />
In this column the Addressing mode is configured. The choices are "DHCP client", "AutoIP" and "Static".<br />
<br />
===IP address===<br />
Here you set the static IP address if you have selected "Static" as the Addressing mode.<br />
<br />
===Netmask===<br />
Here you set the netmask if you have selected "Static" as the Addressing mode.<br />
<br />
===Default route===<br />
Here you set the default route if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. The default route is the route that takes effect when no other route is available for an IP destination address.<br />
<br />
===Name Server (DNS)===<br />
Here you set the Name Server if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. Here you set the name of the DNS protocol.<br />
<br />
===Name===<br />
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.<br />
<br />
===Comment===<br />
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.<br />
<br />
==The Miscellaneous Section==<br />
[[File:Screenshot from 2024-09-16 09-49-47.png|thumb|Miscellaneous]]<br />
This section is available for WCUs with version 2.49 or later.<br />
===Set digital out 3 on boot=== <br />
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).<br />
<br />
===Diagnostic tester priority===<br />
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".<br />
<br />
=== Allow ethernet activation on WCU ===<br />
For WCUs of version 2.90.4 or later it is possible to choose whether or not to allow the WCU to use ethernet activation. Not allowing this might disturb some of the WCUs features.<br />
<br />
===Set 5V out on boot===<br />
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.<br />
<br />
===Activate buzzer on detected digital input change===<br />
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.<br />
<br />
=== Diagnostic firewall disable and PIN ===<br />
Option to disable diagnostic firewall. Requires PIN. Visible for WCUs with version 2.89.0 or later.<br />
<br />
=== Diagnostic tester detection ===<br />
Option to detect any diagnostic testers that they may not be interrupted, typically during OTA. Available for WCUs with version 2.96.0 or later.<br />
<br />
==Manage templates==<br />
[[File:Io config2.png|thumb|frame|Selecting Template]]<br />
Admins can save configs as templates (see [[#Manage templates (for admins) | Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.<br />
Clicking "Apply" will apply the selected template. You can always change settings or add more info, the template could be anything you need or just act as a starting point.<br />
<br />
If WMUs are enabled in the portal, a template will save the CANs from each WMU and when a template is selected the WMU CANs are applied 1:1 to each existing WMU in the configuration. <br />
If there are no WMUs in the configuration the template's WMU CANs will not be applied, only the WCU's CANs.<br />
<br />
==Manage templates (for admins)==<br />
[[File:Io config3.png|thumb|frame|Manage Templates (admin view)]]<br />
[[File:Io config4.png|thumb|frame|Manage Templates (with WMUs enabled)]]<br />
If you are an admin you have an extra button "Save current config as template" in the Manage configuration templates window. Clicking it to save the current configuration as a template will prompt you for a name. If the name already exists (case insensitive) a confirmation dialog will popup before overwriting.<br />
<br />
Additionally, as admin you will be able to remove existing templates, which is done by clicking the red "Remove record" icon to the right of the template name. A confirmation dialog will popup to prevent deletion by mistake.<br />
<br />
==Show Vehicle Profile==<br />
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]<br />
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.<br />
<br />
== Check PINs ==<br />
Requires version 2.89.0 or later. Pressing '''Check PINs''' for a WCU will lookup existing PINs for HIA, HIB, and Diagnostic firewall disable. If available the PINs will be applied to their corresponding fields. If not all PINs are available there will be a pop-up specifying which PINs are unavailable and for which reason: either missing entirely or there exists a PIN for the ECU but for the wrong service area.<br />
<br />
For resource groups '''Check PINs''' will not apply any found PINs, instead if there are any resources with missing PINs it will specify, like for individual WCUs, which PINs are missing and for which WCUs.<br />
<br />
To apply PINs for resource groups see [[I/O configurations#Apply uploaded PINs|apply uploaded PINs]] below.<br />
== Apply uploaded PINs ==<br />
Option for resource groups to apply uploaded PINs for HIA, HIB, and Diagnostic firewall disable. Resets back to unchecked after saving the configuration. Visible for WCUs with version 2.89.0 or later.<br />
<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). As of 2.94.0 the PINs may also be fetched from PIE via ''Administration''->''Resource group''s'','' read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Creating_a_Task&diff=4095Creating a Task2025-11-06T15:08:36Z<p>Robin.karhu: /* Software version validation (Available from version 2.74.0) */</p>
<hr />
<div><includeonly>== Creating a Task==</includeonly><br />
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of task you want to create. Note that it is not possible to create a new task for a WCU which has the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU has the latter label, it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of 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. <br />
<br />
To learn about how to add resources to the task, check [[New task|here]].<br />
<br />
== Arcos ==<br />
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]<br />
The WICE system can interact with external loggers as well. From version 2.71 the portal can interact with the Arcos-logger from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.ccmc''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.<br />
<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the Arcos - no upload will be required.<br />
<br />
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]]).<br />
<br />
== Area5 ==<br />
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]<br />
Area5 tasks are used to read out data from the memory of ECUs. <br />
<br />
'''Assignment:''' To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. <br />
<br />
'''Validate ECU SW version on WCU:''' By checking this box, the WCU will validate that the ECU SW version of the task and the actual ECU are the same before starting the task. If they are different, it will not start the task.<br />
<br />
'''Trigger Expression:''' The task can be started by an expression. This option lets the user specify start trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). For an explanation of trigger conditions look [[Server Trigger|here]].<br />
<br />
'''Sync Signal:''' It is possible to specify a signal with given values that will be sent when the Area5 task starts and stops. This can be used to synchronize the Area5 read-out with external measurements systems like the M-Log.<br />
<br />
== Audio ==<br />
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:<br />
* '''Trigger button''': to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.<br />
* '''Signal reader''': initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader '''recorder''' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the audio recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. <br />
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of triggers look [[Server Trigger|here]].<br />
* '''Audio level''': Start the trigger once the microphone registers volume above a certain threshold.<br />
* '''None''': start the recording as soon as possible.<br />
<br />
In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.<br />
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. <br />
<br />
There is more information about audio in WICE [[Wice audio|here]].<br />
<br />
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
== Blue piraT ==<br />
The blue PiraT is a measurement system from Telemotive AG that can be configured with measurement set-ups, and data accessed through the WICE Portal. Note that to use the blue PiraT module, the WCUs to be used need to be preconfigured with a special software package (i.e. an "extra bundle"). Contact Alkit Communications in order to set this up.<br />
<br />
== CAN-recorder ==<br />
[[File:Canrecorder.png|thumb|Canrecorder]]<br />
Canrecorder is a measurement module that allows CAN frames to be captured and logged.<br />
<br />
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.<br />
<br />
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”<br />
<br />
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. <br />
<br />
===Scheduling=== <br />
<br />
For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached. By selecting the "On ignition" checkbox, the task will be performed once on ignition. If delay is above 0 then the task will be performed once the configured amount of seconds have passed after ignition.<br />
<br />
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]<br />
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with 'On ignition' enabled]]<br />
<br clear="all"><br />
<br />
To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the [[The Portal Administrator View#The Vehicles Tab|Vehicles panel]]. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.<br />
<br />
== Diagnostic Log and Trace (DLT) ==<br />
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 "DLT UDS mode". <br />
[[File:DLT multi task and vehicle announcement.png|thumb|DLT multi task and get DLT Daemon address from vehicle announcement]]<br />
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 "Enable multi task" checkbox as can be seen in the screenshot the right. <br />
<br />
=== DLT Daemon Mode ===<br />
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]. <br />
<br />
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. <br />
<br />
So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:<br />
<br />
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon. Check "Use vehicle announcement" (available from version 2.96.0) to get the address from vehicle announcement instead. See screenshot to the right.<br />
# Daemon port - which port on the address the daemon is at.<br />
# 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].<br />
<br />
=== DLT UDS Mode ===<br />
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 "Add transfer". An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number, an optional pin code (more on this later) and the directory to fetch. You can add as many entries as you wish.<br />
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]<br />
There is a check box with the text "Use vehicle specific PINs". By checking the box, the system will try to get a vehicle specific PIN code for each ECU and WCU. The type of PIN for this service is area 19. How to supply the system with such PIN codes is described [[Vehicles#Upload Vehicle pins|here]].<br />
<br />
There is also a button "Check PINs" available to resource groups that will—if the above check box is checked—look for any missing PINs in the portal for the configured ECUs.<br />
<br />
== ETAS ==<br />
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.<br />
<br />
When creating an ETAS task, the task description file you select must be a .exp file.<br />
<br />
== Ethernet capture ==<br />
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]].<br />
<br />
== File fetcher ==<br />
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]<br />
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.<br />
<br />
The following needs to be specified when creating such a task:<br />
<br />
* '''File path''' - One or several paths to a files or file-containing directories on the unit's file system. This specifies which files that will be fetched.<br />
* '''Username''' - To log in to the unit.<br />
* '''Password''' - To log in to the unit.<br />
* '''IP address''' - To find the unit.<br />
* '''Port''' - To find the unit. Default is 22, but can be changed.<br />
<br />
Furthermore, the task also allows the use of a proxy.<br />
<br />
To use a proxy, the '''Use Proxy''' checkbox has to be checked, and the following must be specified:<br />
<br />
* '''Proxy Username''' - To log in to the proxy unit.<br />
* '''Proxy Password''' - To log in to the proxy unit.<br />
* '''Proxy IP Address''' - To find the proxy unit.<br />
* '''Proxy Port''' - To find the proxy unit. Default is 22, but can be changed.<br /><br />
== IDC ==<br />
The Internal Diagnostic Client (IDC) is a measurement module that allows a sequence of diagnostic requests to be sent and responses recorded. The sequence of diagnostic requests can be created as an assignment in the Assignment tab, alternatively can be uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
== IPEmotion RT ==<br />
The WICE system can interact with external loggers as well. From version 2.72 the portal can interact with the logger IPEmotion RT from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.irf''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.<br />
<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.<br />
<br />
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]]).<br />
<br />
== LPD ==<br />
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.<br />
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]<br />
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]<br />
From version 2.83.0 of the WICE portal the task measurement file can be updated via the View Task function in the Tasks tab and a dialog as shown to the right will appear. By pressing the "Edit" button in the lower right corner, you will be presented with the possibility to upload a new measurement task file. This is shown with a red triangle in the illustration on the right.<br />
<br />
== M-Log ==<br />
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]]<br />
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the MLOG - no upload will be required.<br />
<br />
==== Software version validation (Available from version 2.74.0) ====<br />
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. <br />
<br />
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 "Add" button. The data you just entered will be added to the table and evaluated against what the WICE system has read out from the vehicle. In the example to the right something is incorrect which is indicated by the yellow color. To see the exact reason, simply use the cursor to see the specific message. <br />
<br />
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 "Submit". <br />
<br />
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. <br />
<br />
== MQTT ==<br />
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.<br />
<br />
== Rapid prototyping ==<br />
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]].<br />
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]<br />
The rapid prototyping tab can be seen in Figure "Rapid prototyping task". <br />
<br />
An RP task must consist of at least an 'RP binary' or a 'Web application zip file'.<br />
<br />
== SoftHub ==<br />
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.<br />
<br />
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. <br />
<br />
The SoftHub task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''server triggers''' to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].<br />
<br />
== Signal Reader == <br />
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]<br />
Signal Reader is a data capture module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data, and ECU-internal signals read by CCP or XCP. To create a Signal Reader task you proceed as follows:<br />
<br />
1. You either select an assignment file of .haf format, or choose an assignment created in the assignment creator (see [[Signal Reader Assignment Wizard]]). Your current choice will be displayed in the "Chosen file" field.<br />
<br />
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]].<br />
<br />
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting "Monitor signals". When selected, two boxes will appear under the task description. In the left one you search for signals and drag them over to the right one where the signals to be monitored are listed. You can later see the monitored signals by pressing the '''Monitor Signals''' button either in the Tasks tab or in the Vehicles tab. It is also possible to copy the signals text in the bottom right corner of the right box. Next to the copy text button you can also paste signals as text where the pasted signal names will be matched against the list of unselected signals<br />
<br />
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).<br />
<br />
5. The Signal Reader task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''Server Triggers''' to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].<br />
<br />
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
=== The Signal Broker === <br />
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]].<br />
<br />
=== Files containing references to sequence files === <br />
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] <br />
If the measurement file contains references to sequence files, you are also required to select these in order to run the task. The portal scans the .haf file for such entries and presents this to you, see illustration 4.2. Click the button for each sequence file reference to upload each sequence file needed. Some requests in the sequence file may be for reading DTCs, and in such cases you can select the option of also reading associated ''Snapshots'' or ''Extended data''. An example of this can found in Figure "Sequence Files References in .haf File". <br />
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] <br />
<br />
Here, the .haf file contained two references to sequence files. As no sequence files have yet been uploaded, the selection for reading snapshot or extended data is grayed out. In Figure "Sequence File with Functional Query" we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read ''Extended data''. It is also possible to select both ''Snapshots'' and ''Extended data''. <br />
<br><br />
<br />
=== WICE internal signals ===<br />
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]]<br />
<br />
== SoH ==<br />
[[File:SoH.png|thumb|799x799px|SoH]]<br />
A State of Health (SoH) task collects specific status information from vehicles. You select which information you want the task to collect by filling in one or more of the checkboxes shown in Figure "SoH". The number of checkboxes shown can vary depending on the WICE installation. In order for SoH data to be correctly interpreted, relevant description files (e.g. SDDB) for the vehicles executing the SoH task may have to been available. To add such a description file for a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:<br />
*Mileage<br />
*Voltage<br />
*Read ECU software numbers<br />
*Read ECU DTC:s (optionally including 'Snapshot' and 'Extended data')<br />
*Read OBD-II PIDs<br />
*App Diagnotstic Db Part Num<br />
*Build ID<br />
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]<br />
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)<br />
*Clear DTCs. <br />
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)<br />
**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)<br />
*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 'engine_hours' (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle. <br />
<br />
This task can also be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
Some selections above might not be available to you as this is a configuration setting depending on customer.<br />
<br />
== SWDL ==<br />
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]<br />
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table. <br />
<br />
SWDL tasks can optionally include a '''pre-update sequence file and/or a post-update sequence file'''. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.<br />
<br />
SWDL tasks can optionally include one '''signature file''' (containing checksums). The file is assumed to be an xml file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)<br />
<br />
SWDL tasks can optionally include a '''VGM unlock''' access control mechanism, with a PIN code for the VGM node. This is specifically for vehicles requiring this kind of access control for ECU re-programming.<br />
<br />
By checking the box '''Run SoH after completion''' it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.<br />
<br />
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "'''Use Vehicle Pin mappings'''". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].<br />
<br />
SWDL tasks can optionally contain a '''Trigger Expression''' which must be fulfilled within a specified time limit ("Wait time") for ECU re-programming to be allowed. The trigger expression follows the same syntax as Signal Reader trigger expressions (or [[Server Trigger|Server Triggers]], audio/video triggers), and should be built up from signals being measured in a Signal Reader assignment. The user must make sure that there is a Signal Reader assignment on the WCUs of the SWDL task, with the signals of the trigger expression being measured.<br />
<br />
<br />
It is also possible to choose to '''ignore checksums''' and/or '''disable pre-programming''' using the corresponding checkboxes.<br />
<br />
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).<br />
<br />
== Video ==<br />
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:<br />
* '''Trigger button''': To initiate the recording you need to attach a button to the WCU in order to start in the video recording.<br />
* '''Signal reader''': Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader ''recorder'' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the video recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. <br />
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of how to enter triggers, have a look [[Server Trigger|here]].<br />
* '''None''': start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)<br />
<br />
In addition to this, you can set the '''pre-trig''' time (not valid in the cases of the 'None' trigger option above). As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the video has already been recorded for the number of seconds specified.<br />
<br />
A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.<br />
<br />
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.<br />
<br />
Read more about the video support in WICE [[WICE_video|here]].<br />
<br />
== Applicable for all types ==<br />
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]].<br />
<br />
=== Site specific features ===<br />
<br />
==== Announce result file availability ====<br />
[[File:Resultfilepanel.png|thumb|Announced On column]]<br />
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there's a new 'Announced On' column that keeps track of when the result file was announced.<br />
<br />
==== Retention time ====<br />
[[File:Retention time.png|thumb|435x435px|Retention time]]<br />
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. <br />
<br />
It is possible to set a default retention time for resource groups. To do this, add a global value label named '''RETENTION_TIME''' to the resource group and give it an appropriate value. This value will then be used as a template value when creating a new task for this resource group. If multiple resource groups have this label and they have different values, the one with the lowest/shortest retention time value will be chosen as the template value.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.96&diff=4094New features in v2.962025-11-06T15:03:50Z<p>Robin.karhu: /* Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks */</p>
<hr />
<div>This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.<br />
<br />
== DLT Daemon mode and DLT UDS in parallel ==<br />
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).]]<br />
<br />
== DLT Daemon address via vehicle announcement ==<br />
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).]]<br />
<br />
== Set, View, and Apply Default WCU Configurations ==<br />
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]].<br />
<br />
== Users can now shelve a WCU directly from the Vehicles panel ==<br />
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]].<br />
<br />
== VINReader option to not request VIN if known ==<br />
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.<br />
<br />
== Support for diagnostic Build ID request ==<br />
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.<br />
<br />
== Diagnostic tester detection ==<br />
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the IO tab when editing the configuration.<br />
<br />
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==<br />
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.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.96&diff=4093New features in v2.962025-11-06T15:02:58Z<p>Robin.karhu: </p>
<hr />
<div>This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.<br />
<br />
== DLT Daemon mode and DLT UDS in parallel ==<br />
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).]]<br />
<br />
== DLT Daemon address via vehicle announcement ==<br />
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).]]<br />
<br />
== Set, View, and Apply Default WCU Configurations ==<br />
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]].<br />
<br />
== Users can now shelve a WCU directly from the Vehicles panel ==<br />
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]].<br />
<br />
== VINReader option to not request VIN if known ==<br />
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.<br />
<br />
== Support for diagnostic Build ID request ==<br />
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.<br />
<br />
== Diagnostic tester detection ==<br />
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the IO tab when editing the configuration.<br />
<br />
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==<br />
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|MLog]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.96&diff=4092New features in v2.962025-11-06T15:02:43Z<p>Robin.karhu: </p>
<hr />
<div>This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.<br />
<br />
== DLT Daemon mode and DLT UDS in parallel ==<br />
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).]]<br />
<br />
== DLT Daemon address via vehicle announcement ==<br />
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).]]<br />
<br />
== Set, View, and Apply Default WCU Configurations ==<br />
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]].<br />
<br />
== Users can now shelve a WCU directly from the Vehicles panel ==<br />
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]].<br />
<br />
== VINReader option to not request VIN if known ==<br />
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.<br />
<br />
== Support for diagnostic Build ID request ==<br />
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.<br />
<br />
== Diagnostic tester detection ==<br />
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the IO tab when editing a configuration.<br />
<br />
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==<br />
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|MLog]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.96&diff=4091New features in v2.962025-11-06T15:02:16Z<p>Robin.karhu: </p>
<hr />
<div>This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.<br />
<br />
== DLT Daemon mode and DLT UDS in parallel ==<br />
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).]]<br />
<br />
== DLT Daemon address via vehicle announcement ==<br />
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).]]<br />
<br />
== Set, View, and Apply Default WCU Configurations ==<br />
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]].<br />
<br />
== Users can now shelve a WCU directly from the Vehicles panel ==<br />
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]].<br />
<br />
== VINReader option to not request VIN if known ==<br />
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.<br />
<br />
== Support for diagnostic Build ID request ==<br />
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.<br />
<br />
== Diagnostic tester detection ==<br />
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the IO tab of edit configuration.<br />
<br />
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==<br />
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|MLog]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.96&diff=4090New features in v2.962025-11-06T15:01:57Z<p>Robin.karhu: </p>
<hr />
<div>This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.<br />
<br />
== DLT Daemon mode and DLT UDS in parallel ==<br />
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).]]<br />
<br />
== DLT Daemon address via vehicle announcement ==<br />
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).]]<br />
<br />
== Set, View, and Apply Default WCU Configurations ==<br />
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]].<br />
<br />
== Users can now shelve a WCU directly from the Vehicles panel ==<br />
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]].<br />
<br />
== VINReader option to not request VIN if known ==<br />
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.<br />
<br />
== Support for diagnostic Build ID request ==<br />
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.<br />
<br />
== Use diagnostic tester detection ==<br />
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the IO tab of edit configuration.<br />
<br />
== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==<br />
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|MLog]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicles&diff=4011Vehicles2025-08-28T11:51:04Z<p>Robin.karhu: /* Right click context menu */</p>
<hr />
<div><includeonly>=Vehicles Tab=</includeonly><br />
This view is used to handle the various vehicles that are assigned to you. A figure of this view<br />
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you<br />
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your<br />
criteria a row count is presented in the upper right area to show how many potential matches<br />
there are. The entries are also fetched as you type but only as many rows as fit your current<br />
view are fetched. As you scroll down more results will be fetched.<br />
<br />
[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]<br />
<br />
The number of possible columns to show is quite large. You can select which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
|'''Active alarms'''<br />
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.<br />
|-<br />
| style="font-weight: bold;" | <span id="Connected">Connected</span><br />
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Distance">Distance</span><br />
| Shows the distance the car has been driven the last week. (SoH task specific)<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_DRO">Last DRO</span><br />
| Says when the DRO log file was last transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_log">Last log</span><br />
| Shows when the last log file was transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Mileage">Mileage</span><br />
| The column shows the mileage of the car.<br />
|-<br />
| style="font-weight: bold;" | <span id="Plate_number">Plate number</span><br />
| The plate number of the car where the WCU is mounted.<br />
|-<br />
|'''Platform type'''<br />
|Search WCU by platform type.<br />
|-<br />
| style="font-weight: bold;" | <span id="Project_Id">Project Id</span><br />
| Shows the project identification number.<br />
|-<br />
| style="font-weight: bold;" | <span id="Proto_number">Proto number</span><br />
| Shows the proto number.<br />
|-<br />
|'''Resource group'''<br />
|The resource group (if any) the WCU is part of.<br />
|-<br />
| style="font-weight: bold;" | <span id="Series">Series</span><br />
| Shows the series attribute.<br />
|-<br />
| style="font-weight: bold;" | <span id="TSU">TSU</span><br />
| Shows the TSU identifier.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload">Upload</span><br />
| This column says how much data has been transferred from the WCU to the portal the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_date">Upload date</span><br />
| Contains which date the last upload was done<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_size">Upload size</span><br />
| Says what the size, in kilobytes, of the last data upload was.<br />
|-<br />
| style="font-weight: bold;" | <span id="Up-time">Uptime</span><br />
| Shows how many hours the WCU been running the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="VIN">VIN</span><br />
| Shows the Vehicle Identification Number of the car where the WCU is mounted.<br />
|-<br />
| style="font-weight: bold;" | <span id="Voltage">Voltage </span><br />
| The column shows the latest known battery voltage as reported by the CEM.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_ID">WCU ID</span><br />
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Description">WCU Description</span><br />
| A textual comment attached to the WCU.<br />
|-<br />
|'''WCU Firmware'''<br />
|Shows which firmware the WCU uses.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_voltage">WCU voltage</span><br />
| Shows the voltage as measured by the WCU.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Version">WCU Version</span><br />
| Shows which version the current WCU software has.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_storage_usage">WCU storage usage</span><br />
| Shows the amount of storage available to store data on the WCU.<br />
|-<br />
|'''WCU name'''<br />
|Shows the name of the WCU.<br />
|-<br />
|'''WCU state'''<br />
|Shows the current state of the WCU.<br />
|}<br />
<br />
Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].<br />
<br />
There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating tasks you can select a resource group instead of the individual WCU:s to start a new task. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row<br />
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.<br />
<br />
When selecting a row in the table the selected row changes to a blue shade. You can modify<br />
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.<br />
<br />
== Right click context menu ==<br />
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu with several options, some of which are described here.<br />
<br />
''' Go to Tasks Panel ''' <br> <br />
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.<br />
<br />
''' Go to Search Panel ''' <br><br />
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.<br />
<br />
''' Go to Timeline ''' <br><br />
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.<br />
<br />
''' Go to alarms ''' <br><br />
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.<br />
<br />
'''Upload vehicle pins'''<br />
<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will upload the pin AA:BB:CC:DD:EE for an ECU 0x1D0D (i.e. HIA) with service area 0x5. This PIN will then be associated to the vehicle connected to the WCU.<br />
<br />
'''Compare WCU configurations'''<br />
<br />
Selecting this on a single WCU will open a dialog where you may choose other WCUs to compare against the selected WCU. Once compared, the result panel that is opened will show each WCUs configuration variables that differ from the selected WCUs configuration.<br />
<br />
''' Remove WCU(s) from Resource Group ''' <br><br />
If WCUs which are included in a resource group are selected, the menu option "Remove WCU(s) from Resource Group" will appear. They do not have to be in the same resource group as each other. If a resource which do not fulfill this requirement is selected in addition, this option will not be visible.<br />
<br />
'''Show WCU history'''<br />
[[File:ShowWCUHistoryUpdatedAgain.png|alt=|thumb|Example of a Show WCU history]]<br />
Selecting this shows a window with the history of the selected WCU. The following columns will be displayed in the window:<br />
<br />
* Change date - Displays the date the WCU was changed.<br />
*Type of change- Displays whether the update involved a configuration change, a tools change, or a label change.<br />
* Description - Displays a description of the WCU.<br />
* Active - Shows if the WCU is active or not.<br />
* WCU ID - Shows the WCU ID.<br />
* WCU name - Displays the WCU name.<br />
* WCU version - The WCU version.<br />
* WCU firmware version - The WCU firmware version.<br />
* Changed by - The user who modified the WCU.<br />
* Resource group - The resource group.<br />
* ICCID - The SIM card installed.<br />
*State - reflects the WCU’s status at the time of the change. Possible states include: ''In Operation'', ''Shelving in Progress'', ''Shelved'', ''Shelving Refurbish in Progress'', and ''Shelving Refurbish Done.''<br />
* Modem ID - Shows the Modem ID. (This is hidden by default but can be revealed by right-clicking a column and selecting the "Columns" drop down menu.). <br />
<br />
For the Show WCU history option to be available only a single WCU can be selected.<br />
<br />
'''Trigger upload now'''<br />
<br />
Momentarily stop the WCU, offload it and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger reboot now'''<br />
<br />
Reboots the trigger and WCU. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger collect and upload'''<br />
<br />
This action will cause the task to momentarily stop and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.45.<br />
<br />
'''Trigger VIN readout'''<br />
<br />
Trigger VIN readout, this action will cause the task to momentarily stop .This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.65.<br />
<br />
==New task==<br />
To create a new task for all selected WCUs, click the button [[New task|New Task]]. To learn more about creating each specific task see [[Creating a Task]].<br />
<br />
== Upload Vehicle pins ==<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><VIN>;<ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>WICE_VIN_1;1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will save the pin AA:BB:CC:DD:EE for the ECU 0x1D0D (i.e. HIA) with service area 0x5 and will be associated with the vehicle WICE_VIN_1.<br />
<br />
==Show the Vehicle Position==<br />
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in. <br />
<br />
If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]]. <br />
<br />
==View Diagnostic Trouble Codes==<br />
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]<br />
<br />
If an SoH task has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle. <br />
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.<br />
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".<br />
<br />
==View ECU software==<br />
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]<br />
It is possible to see the ECU software number for each ECU in a vehicle.<br />
Press the button “ECU SW” after you have selected one vehicle. The following view will be<br />
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with<br />
when it was read. You can download the list as a tab-separated text file if you press “Download”.<br />
<br />
==Get WCU Up-time==<br />
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]<br />
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.<br />
<br />
Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.<br />
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.<br />
<br />
From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].<br />
<br />
==Export SoH Data==<br />
[[File:Soh data export.png|frame|SoH Data Export Panel]]<br />
You can export data from SoH tasks to your local computer by using the function<br />
“Export SoH data”. Select the cars you are interested in as you can export for more than<br />
one car in one export.<br />
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage, storage usage and diagnostic trouble codes. <br />
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.<br />
<br />
==Resource Groups==<br />
WCUs and cars can collectively be referred to as "resources". As such they can be grouped<br />
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only<br />
one type of resource is in a resource group.<br />
<br />
You identify a resource group by a gray arrow like icon to the left in the table row. If you<br />
click the icon the entry opens up and makes room for showing which resources are part<br />
of the resource group.<br />
<br />
From version 2.42 viewing the resource group's resources has been improved. More info can be found in [[Resource group's resources]].<br />
<br />
When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a<br />
resource group or not. If you select a resource group, the new task will be downloaded to all the WCUs that are part of the resource group.<br />
As a regular user you can not create and remove resource groups, only an administrator<br />
of the portal can do this.<br />
<br />
From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.<br />
<br />
This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.<br />
<br />
Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".<br />
<br />
==Modules==<br />
If you have the right permission you will be able to view a WCU:s modules, and<br />
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:<br />
<br />
* [[The Portal Administrator View#configure the area5 module|Area5]]<br />
* [[The Portal Administrator View#Configure the audio module|Audio]]<br />
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]<br />
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]<br />
* [[DLT Module|DLT]]<br />
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]<br />
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]<br />
* [[The Portal Administrator View#Configure the File fetcher module|File Fetcher]]<br />
* [[The Portal Administrator View#Configure the GPS Module|GPS]]<br />
* [[The Portal Administrator View#Configure the IDC Module|IDC]]<br />
* [[The Portal Administrator View#Configure the IPEmotion RT Module|IPEmotion RT]]<br />
* [[The Portal Administrator View#Configure the LPD Module|LPD]]<br />
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]<br />
* [[The Portal Administrator View#Configure the M-log Module|M-log]]<br />
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]<br />
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]<br />
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]<br />
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]<br />
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]<br />
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]<br />
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]<br />
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]<br />
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]<br />
* [[The Portal Administrator View#Configure the Video Module|Video]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicles&diff=4010Vehicles2025-08-28T11:49:56Z<p>Robin.karhu: /* Right click context menu */</p>
<hr />
<div><includeonly>=Vehicles Tab=</includeonly><br />
This view is used to handle the various vehicles that are assigned to you. A figure of this view<br />
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you<br />
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your<br />
criteria a row count is presented in the upper right area to show how many potential matches<br />
there are. The entries are also fetched as you type but only as many rows as fit your current<br />
view are fetched. As you scroll down more results will be fetched.<br />
<br />
[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]<br />
<br />
The number of possible columns to show is quite large. You can select which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
|'''Active alarms'''<br />
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.<br />
|-<br />
| style="font-weight: bold;" | <span id="Connected">Connected</span><br />
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Distance">Distance</span><br />
| Shows the distance the car has been driven the last week. (SoH task specific)<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_DRO">Last DRO</span><br />
| Says when the DRO log file was last transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_log">Last log</span><br />
| Shows when the last log file was transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Mileage">Mileage</span><br />
| The column shows the mileage of the car.<br />
|-<br />
| style="font-weight: bold;" | <span id="Plate_number">Plate number</span><br />
| The plate number of the car where the WCU is mounted.<br />
|-<br />
|'''Platform type'''<br />
|Search WCU by platform type.<br />
|-<br />
| style="font-weight: bold;" | <span id="Project_Id">Project Id</span><br />
| Shows the project identification number.<br />
|-<br />
| style="font-weight: bold;" | <span id="Proto_number">Proto number</span><br />
| Shows the proto number.<br />
|-<br />
|'''Resource group'''<br />
|The resource group (if any) the WCU is part of.<br />
|-<br />
| style="font-weight: bold;" | <span id="Series">Series</span><br />
| Shows the series attribute.<br />
|-<br />
| style="font-weight: bold;" | <span id="TSU">TSU</span><br />
| Shows the TSU identifier.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload">Upload</span><br />
| This column says how much data has been transferred from the WCU to the portal the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_date">Upload date</span><br />
| Contains which date the last upload was done<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_size">Upload size</span><br />
| Says what the size, in kilobytes, of the last data upload was.<br />
|-<br />
| style="font-weight: bold;" | <span id="Up-time">Uptime</span><br />
| Shows how many hours the WCU been running the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="VIN">VIN</span><br />
| Shows the Vehicle Identification Number of the car where the WCU is mounted.<br />
|-<br />
| style="font-weight: bold;" | <span id="Voltage">Voltage </span><br />
| The column shows the latest known battery voltage as reported by the CEM.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_ID">WCU ID</span><br />
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Description">WCU Description</span><br />
| A textual comment attached to the WCU.<br />
|-<br />
|'''WCU Firmware'''<br />
|Shows which firmware the WCU uses.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_voltage">WCU voltage</span><br />
| Shows the voltage as measured by the WCU.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Version">WCU Version</span><br />
| Shows which version the current WCU software has.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_storage_usage">WCU storage usage</span><br />
| Shows the amount of storage available to store data on the WCU.<br />
|-<br />
|'''WCU name'''<br />
|Shows the name of the WCU.<br />
|-<br />
|'''WCU state'''<br />
|Shows the current state of the WCU.<br />
|}<br />
<br />
Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].<br />
<br />
There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating tasks you can select a resource group instead of the individual WCU:s to start a new task. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row<br />
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.<br />
<br />
When selecting a row in the table the selected row changes to a blue shade. You can modify<br />
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.<br />
<br />
== Right click context menu ==<br />
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu with several options, some of which are described here.<br />
<br />
''' Go to Tasks Panel ''' <br> <br />
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.<br />
<br />
''' Go to Search Panel ''' <br><br />
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.<br />
<br />
''' Go to Timeline ''' <br><br />
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.<br />
<br />
''' Go to alarms ''' <br><br />
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.<br />
<br />
'''Upload vehicle pins'''<br />
<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will upload the pin AA:BB:CC:DD:EE for an ECU 0x1D0D (i.e. HIA) with service area 0x5. This PIN will then be associated to the vehicle connected to the WCU.<br />
<br />
'''Compare WCU configurations'''<br />
<br />
Selecting this on a single WCU will open a dialog where you may choose other WCUs to compare against the selected WCU. Once compared, the result panel that is opened will show whichever configuration variables of the WCUs that differ from the selected WCUs configuration.<br />
<br />
''' Remove WCU(s) from Resource Group ''' <br><br />
If WCUs which are included in a resource group are selected, the menu option "Remove WCU(s) from Resource Group" will appear. They do not have to be in the same resource group as each other. If a resource which do not fulfill this requirement is selected in addition, this option will not be visible.<br />
<br />
'''Show WCU history'''<br />
[[File:ShowWCUHistoryUpdatedAgain.png|alt=|thumb|Example of a Show WCU history]]<br />
Selecting this shows a window with the history of the selected WCU. The following columns will be displayed in the window:<br />
<br />
* Change date - Displays the date the WCU was changed.<br />
*Type of change- Displays whether the update involved a configuration change, a tools change, or a label change.<br />
* Description - Displays a description of the WCU.<br />
* Active - Shows if the WCU is active or not.<br />
* WCU ID - Shows the WCU ID.<br />
* WCU name - Displays the WCU name.<br />
* WCU version - The WCU version.<br />
* WCU firmware version - The WCU firmware version.<br />
* Changed by - The user who modified the WCU.<br />
* Resource group - The resource group.<br />
* ICCID - The SIM card installed.<br />
*State - reflects the WCU’s status at the time of the change. Possible states include: ''In Operation'', ''Shelving in Progress'', ''Shelved'', ''Shelving Refurbish in Progress'', and ''Shelving Refurbish Done.''<br />
* Modem ID - Shows the Modem ID. (This is hidden by default but can be revealed by right-clicking a column and selecting the "Columns" drop down menu.). <br />
<br />
For the Show WCU history option to be available only a single WCU can be selected.<br />
<br />
'''Trigger upload now'''<br />
<br />
Momentarily stop the WCU, offload it and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger reboot now'''<br />
<br />
Reboots the trigger and WCU. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger collect and upload'''<br />
<br />
This action will cause the task to momentarily stop and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.45.<br />
<br />
'''Trigger VIN readout'''<br />
<br />
Trigger VIN readout, this action will cause the task to momentarily stop .This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.65.<br />
<br />
==New task==<br />
To create a new task for all selected WCUs, click the button [[New task|New Task]]. To learn more about creating each specific task see [[Creating a Task]].<br />
<br />
== Upload Vehicle pins ==<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><VIN>;<ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>WICE_VIN_1;1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will save the pin AA:BB:CC:DD:EE for the ECU 0x1D0D (i.e. HIA) with service area 0x5 and will be associated with the vehicle WICE_VIN_1.<br />
<br />
==Show the Vehicle Position==<br />
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in. <br />
<br />
If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]]. <br />
<br />
==View Diagnostic Trouble Codes==<br />
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]<br />
<br />
If an SoH task has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle. <br />
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.<br />
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".<br />
<br />
==View ECU software==<br />
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]<br />
It is possible to see the ECU software number for each ECU in a vehicle.<br />
Press the button “ECU SW” after you have selected one vehicle. The following view will be<br />
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with<br />
when it was read. You can download the list as a tab-separated text file if you press “Download”.<br />
<br />
==Get WCU Up-time==<br />
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]<br />
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.<br />
<br />
Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.<br />
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.<br />
<br />
From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].<br />
<br />
==Export SoH Data==<br />
[[File:Soh data export.png|frame|SoH Data Export Panel]]<br />
You can export data from SoH tasks to your local computer by using the function<br />
“Export SoH data”. Select the cars you are interested in as you can export for more than<br />
one car in one export.<br />
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage, storage usage and diagnostic trouble codes. <br />
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.<br />
<br />
==Resource Groups==<br />
WCUs and cars can collectively be referred to as "resources". As such they can be grouped<br />
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only<br />
one type of resource is in a resource group.<br />
<br />
You identify a resource group by a gray arrow like icon to the left in the table row. If you<br />
click the icon the entry opens up and makes room for showing which resources are part<br />
of the resource group.<br />
<br />
From version 2.42 viewing the resource group's resources has been improved. More info can be found in [[Resource group's resources]].<br />
<br />
When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a<br />
resource group or not. If you select a resource group, the new task will be downloaded to all the WCUs that are part of the resource group.<br />
As a regular user you can not create and remove resource groups, only an administrator<br />
of the portal can do this.<br />
<br />
From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.<br />
<br />
This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.<br />
<br />
Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".<br />
<br />
==Modules==<br />
If you have the right permission you will be able to view a WCU:s modules, and<br />
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:<br />
<br />
* [[The Portal Administrator View#configure the area5 module|Area5]]<br />
* [[The Portal Administrator View#Configure the audio module|Audio]]<br />
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]<br />
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]<br />
* [[DLT Module|DLT]]<br />
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]<br />
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]<br />
* [[The Portal Administrator View#Configure the File fetcher module|File Fetcher]]<br />
* [[The Portal Administrator View#Configure the GPS Module|GPS]]<br />
* [[The Portal Administrator View#Configure the IDC Module|IDC]]<br />
* [[The Portal Administrator View#Configure the IPEmotion RT Module|IPEmotion RT]]<br />
* [[The Portal Administrator View#Configure the LPD Module|LPD]]<br />
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]<br />
* [[The Portal Administrator View#Configure the M-log Module|M-log]]<br />
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]<br />
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]<br />
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]<br />
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]<br />
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]<br />
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]<br />
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]<br />
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]<br />
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]<br />
* [[The Portal Administrator View#Configure the Video Module|Video]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicles&diff=4009Vehicles2025-08-28T11:48:50Z<p>Robin.karhu: /* Right click context menu */</p>
<hr />
<div><includeonly>=Vehicles Tab=</includeonly><br />
This view is used to handle the various vehicles that are assigned to you. A figure of this view<br />
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you<br />
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your<br />
criteria a row count is presented in the upper right area to show how many potential matches<br />
there are. The entries are also fetched as you type but only as many rows as fit your current<br />
view are fetched. As you scroll down more results will be fetched.<br />
<br />
[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]<br />
<br />
The number of possible columns to show is quite large. You can select which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
|'''Active alarms'''<br />
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.<br />
|-<br />
| style="font-weight: bold;" | <span id="Connected">Connected</span><br />
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Distance">Distance</span><br />
| Shows the distance the car has been driven the last week. (SoH task specific)<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_DRO">Last DRO</span><br />
| Says when the DRO log file was last transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_log">Last log</span><br />
| Shows when the last log file was transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Mileage">Mileage</span><br />
| The column shows the mileage of the car.<br />
|-<br />
| style="font-weight: bold;" | <span id="Plate_number">Plate number</span><br />
| The plate number of the car where the WCU is mounted.<br />
|-<br />
|'''Platform type'''<br />
|Search WCU by platform type.<br />
|-<br />
| style="font-weight: bold;" | <span id="Project_Id">Project Id</span><br />
| Shows the project identification number.<br />
|-<br />
| style="font-weight: bold;" | <span id="Proto_number">Proto number</span><br />
| Shows the proto number.<br />
|-<br />
|'''Resource group'''<br />
|The resource group (if any) the WCU is part of.<br />
|-<br />
| style="font-weight: bold;" | <span id="Series">Series</span><br />
| Shows the series attribute.<br />
|-<br />
| style="font-weight: bold;" | <span id="TSU">TSU</span><br />
| Shows the TSU identifier.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload">Upload</span><br />
| This column says how much data has been transferred from the WCU to the portal the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_date">Upload date</span><br />
| Contains which date the last upload was done<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_size">Upload size</span><br />
| Says what the size, in kilobytes, of the last data upload was.<br />
|-<br />
| style="font-weight: bold;" | <span id="Up-time">Uptime</span><br />
| Shows how many hours the WCU been running the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="VIN">VIN</span><br />
| Shows the Vehicle Identification Number of the car where the WCU is mounted.<br />
|-<br />
| style="font-weight: bold;" | <span id="Voltage">Voltage </span><br />
| The column shows the latest known battery voltage as reported by the CEM.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_ID">WCU ID</span><br />
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Description">WCU Description</span><br />
| A textual comment attached to the WCU.<br />
|-<br />
|'''WCU Firmware'''<br />
|Shows which firmware the WCU uses.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_voltage">WCU voltage</span><br />
| Shows the voltage as measured by the WCU.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Version">WCU Version</span><br />
| Shows which version the current WCU software has.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_storage_usage">WCU storage usage</span><br />
| Shows the amount of storage available to store data on the WCU.<br />
|-<br />
|'''WCU name'''<br />
|Shows the name of the WCU.<br />
|-<br />
|'''WCU state'''<br />
|Shows the current state of the WCU.<br />
|}<br />
<br />
Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].<br />
<br />
There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating tasks you can select a resource group instead of the individual WCU:s to start a new task. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row<br />
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.<br />
<br />
When selecting a row in the table the selected row changes to a blue shade. You can modify<br />
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.<br />
<br />
== Right click context menu ==<br />
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu with several options, some of which are described here.<br />
<br />
''' Go to Tasks Panel ''' <br> <br />
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.<br />
<br />
''' Go to Search Panel ''' <br><br />
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.<br />
<br />
''' Go to Timeline ''' <br><br />
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.<br />
<br />
''' Go to alarms ''' <br><br />
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.<br />
<br />
'''Upload vehicle pins'''<br />
<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will upload the pin AA:BB:CC:DD:EE for an ECU 0x1D0D (i.e. HIA) with service area 0x5. This PIN will then be associated to the vehicle connected to the WCU.<br />
<br />
'''Compare WCU configurations'''<br />
<br />
Selecting this on a single WCU will open a dialog where you may choose other WCUs to compare against the selected WCU. Once compared, the result panel that is opened will show only the differing configuration variables for the WCUs.<br />
<br />
''' Remove WCU(s) from Resource Group ''' <br><br />
If WCUs which are included in a resource group are selected, the menu option "Remove WCU(s) from Resource Group" will appear. They do not have to be in the same resource group as each other. If a resource which do not fulfill this requirement is selected in addition, this option will not be visible.<br />
<br />
'''Show WCU history'''<br />
[[File:ShowWCUHistoryUpdatedAgain.png|alt=|thumb|Example of a Show WCU history]]<br />
Selecting this shows a window with the history of the selected WCU. The following columns will be displayed in the window:<br />
<br />
* Change date - Displays the date the WCU was changed.<br />
*Type of change- Displays whether the update involved a configuration change, a tools change, or a label change.<br />
* Description - Displays a description of the WCU.<br />
* Active - Shows if the WCU is active or not.<br />
* WCU ID - Shows the WCU ID.<br />
* WCU name - Displays the WCU name.<br />
* WCU version - The WCU version.<br />
* WCU firmware version - The WCU firmware version.<br />
* Changed by - The user who modified the WCU.<br />
* Resource group - The resource group.<br />
* ICCID - The SIM card installed.<br />
*State - reflects the WCU’s status at the time of the change. Possible states include: ''In Operation'', ''Shelving in Progress'', ''Shelved'', ''Shelving Refurbish in Progress'', and ''Shelving Refurbish Done.''<br />
* Modem ID - Shows the Modem ID. (This is hidden by default but can be revealed by right-clicking a column and selecting the "Columns" drop down menu.). <br />
<br />
For the Show WCU history option to be available only a single WCU can be selected.<br />
<br />
'''Trigger upload now'''<br />
<br />
Momentarily stop the WCU, offload it and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger reboot now'''<br />
<br />
Reboots the trigger and WCU. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger collect and upload'''<br />
<br />
This action will cause the task to momentarily stop and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.45.<br />
<br />
'''Trigger VIN readout'''<br />
<br />
Trigger VIN readout, this action will cause the task to momentarily stop .This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.65.<br />
<br />
==New task==<br />
To create a new task for all selected WCUs, click the button [[New task|New Task]]. To learn more about creating each specific task see [[Creating a Task]].<br />
<br />
== Upload Vehicle pins ==<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><VIN>;<ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>WICE_VIN_1;1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will save the pin AA:BB:CC:DD:EE for the ECU 0x1D0D (i.e. HIA) with service area 0x5 and will be associated with the vehicle WICE_VIN_1.<br />
<br />
==Show the Vehicle Position==<br />
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in. <br />
<br />
If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]]. <br />
<br />
==View Diagnostic Trouble Codes==<br />
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]<br />
<br />
If an SoH task has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle. <br />
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.<br />
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".<br />
<br />
==View ECU software==<br />
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]<br />
It is possible to see the ECU software number for each ECU in a vehicle.<br />
Press the button “ECU SW” after you have selected one vehicle. The following view will be<br />
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with<br />
when it was read. You can download the list as a tab-separated text file if you press “Download”.<br />
<br />
==Get WCU Up-time==<br />
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]<br />
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.<br />
<br />
Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.<br />
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.<br />
<br />
From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].<br />
<br />
==Export SoH Data==<br />
[[File:Soh data export.png|frame|SoH Data Export Panel]]<br />
You can export data from SoH tasks to your local computer by using the function<br />
“Export SoH data”. Select the cars you are interested in as you can export for more than<br />
one car in one export.<br />
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage, storage usage and diagnostic trouble codes. <br />
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.<br />
<br />
==Resource Groups==<br />
WCUs and cars can collectively be referred to as "resources". As such they can be grouped<br />
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only<br />
one type of resource is in a resource group.<br />
<br />
You identify a resource group by a gray arrow like icon to the left in the table row. If you<br />
click the icon the entry opens up and makes room for showing which resources are part<br />
of the resource group.<br />
<br />
From version 2.42 viewing the resource group's resources has been improved. More info can be found in [[Resource group's resources]].<br />
<br />
When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a<br />
resource group or not. If you select a resource group, the new task will be downloaded to all the WCUs that are part of the resource group.<br />
As a regular user you can not create and remove resource groups, only an administrator<br />
of the portal can do this.<br />
<br />
From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.<br />
<br />
This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.<br />
<br />
Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".<br />
<br />
==Modules==<br />
If you have the right permission you will be able to view a WCU:s modules, and<br />
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:<br />
<br />
* [[The Portal Administrator View#configure the area5 module|Area5]]<br />
* [[The Portal Administrator View#Configure the audio module|Audio]]<br />
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]<br />
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]<br />
* [[DLT Module|DLT]]<br />
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]<br />
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]<br />
* [[The Portal Administrator View#Configure the File fetcher module|File Fetcher]]<br />
* [[The Portal Administrator View#Configure the GPS Module|GPS]]<br />
* [[The Portal Administrator View#Configure the IDC Module|IDC]]<br />
* [[The Portal Administrator View#Configure the IPEmotion RT Module|IPEmotion RT]]<br />
* [[The Portal Administrator View#Configure the LPD Module|LPD]]<br />
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]<br />
* [[The Portal Administrator View#Configure the M-log Module|M-log]]<br />
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]<br />
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]<br />
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]<br />
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]<br />
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]<br />
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]<br />
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]<br />
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]<br />
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]<br />
* [[The Portal Administrator View#Configure the Video Module|Video]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicles&diff=4008Vehicles2025-08-28T11:48:22Z<p>Robin.karhu: /* Right click context menu */</p>
<hr />
<div><includeonly>=Vehicles Tab=</includeonly><br />
This view is used to handle the various vehicles that are assigned to you. A figure of this view<br />
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you<br />
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your<br />
criteria a row count is presented in the upper right area to show how many potential matches<br />
there are. The entries are also fetched as you type but only as many rows as fit your current<br />
view are fetched. As you scroll down more results will be fetched.<br />
<br />
[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]<br />
<br />
The number of possible columns to show is quite large. You can select which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
|'''Active alarms'''<br />
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.<br />
|-<br />
| style="font-weight: bold;" | <span id="Connected">Connected</span><br />
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Distance">Distance</span><br />
| Shows the distance the car has been driven the last week. (SoH task specific)<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_DRO">Last DRO</span><br />
| Says when the DRO log file was last transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_log">Last log</span><br />
| Shows when the last log file was transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Mileage">Mileage</span><br />
| The column shows the mileage of the car.<br />
|-<br />
| style="font-weight: bold;" | <span id="Plate_number">Plate number</span><br />
| The plate number of the car where the WCU is mounted.<br />
|-<br />
|'''Platform type'''<br />
|Search WCU by platform type.<br />
|-<br />
| style="font-weight: bold;" | <span id="Project_Id">Project Id</span><br />
| Shows the project identification number.<br />
|-<br />
| style="font-weight: bold;" | <span id="Proto_number">Proto number</span><br />
| Shows the proto number.<br />
|-<br />
|'''Resource group'''<br />
|The resource group (if any) the WCU is part of.<br />
|-<br />
| style="font-weight: bold;" | <span id="Series">Series</span><br />
| Shows the series attribute.<br />
|-<br />
| style="font-weight: bold;" | <span id="TSU">TSU</span><br />
| Shows the TSU identifier.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload">Upload</span><br />
| This column says how much data has been transferred from the WCU to the portal the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_date">Upload date</span><br />
| Contains which date the last upload was done<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_size">Upload size</span><br />
| Says what the size, in kilobytes, of the last data upload was.<br />
|-<br />
| style="font-weight: bold;" | <span id="Up-time">Uptime</span><br />
| Shows how many hours the WCU been running the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="VIN">VIN</span><br />
| Shows the Vehicle Identification Number of the car where the WCU is mounted.<br />
|-<br />
| style="font-weight: bold;" | <span id="Voltage">Voltage </span><br />
| The column shows the latest known battery voltage as reported by the CEM.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_ID">WCU ID</span><br />
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Description">WCU Description</span><br />
| A textual comment attached to the WCU.<br />
|-<br />
|'''WCU Firmware'''<br />
|Shows which firmware the WCU uses.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_voltage">WCU voltage</span><br />
| Shows the voltage as measured by the WCU.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Version">WCU Version</span><br />
| Shows which version the current WCU software has.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_storage_usage">WCU storage usage</span><br />
| Shows the amount of storage available to store data on the WCU.<br />
|-<br />
|'''WCU name'''<br />
|Shows the name of the WCU.<br />
|-<br />
|'''WCU state'''<br />
|Shows the current state of the WCU.<br />
|}<br />
<br />
Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].<br />
<br />
There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating tasks you can select a resource group instead of the individual WCU:s to start a new task. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row<br />
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.<br />
<br />
When selecting a row in the table the selected row changes to a blue shade. You can modify<br />
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.<br />
<br />
== Right click context menu ==<br />
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu with several options, some of which are described here.<br />
<br />
''' Go to Tasks Panel ''' <br> <br />
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.<br />
<br />
''' Go to Search Panel ''' <br><br />
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.<br />
<br />
''' Go to Timeline ''' <br><br />
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.<br />
<br />
''' Go to alarms ''' <br><br />
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.<br />
<br />
'''Upload vehicle pins'''<br />
<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will upload the pin AA:BB:CC:DD:EE for an ECU 0x1D0D (i.e. HIA) with service area 0x5. This PIN will then be associated to the vehicle connected to the WCU.<br />
<br />
'''Compare WCU configurations'''<br />
<br />
Selecting this on an individual WCU will open a dialog where you may choose other WCUs to compare against the selected WCU. Once compared, the result panel that is opened will show only the differing configuration variables for the WCUs.<br />
<br />
''' Remove WCU(s) from Resource Group ''' <br><br />
If WCUs which are included in a resource group are selected, the menu option "Remove WCU(s) from Resource Group" will appear. They do not have to be in the same resource group as each other. If a resource which do not fulfill this requirement is selected in addition, this option will not be visible.<br />
<br />
'''Show WCU history'''<br />
[[File:ShowWCUHistoryUpdatedAgain.png|alt=|thumb|Example of a Show WCU history]]<br />
Selecting this shows a window with the history of the selected WCU. The following columns will be displayed in the window:<br />
<br />
* Change date - Displays the date the WCU was changed.<br />
*Type of change- Displays whether the update involved a configuration change, a tools change, or a label change.<br />
* Description - Displays a description of the WCU.<br />
* Active - Shows if the WCU is active or not.<br />
* WCU ID - Shows the WCU ID.<br />
* WCU name - Displays the WCU name.<br />
* WCU version - The WCU version.<br />
* WCU firmware version - The WCU firmware version.<br />
* Changed by - The user who modified the WCU.<br />
* Resource group - The resource group.<br />
* ICCID - The SIM card installed.<br />
*State - reflects the WCU’s status at the time of the change. Possible states include: ''In Operation'', ''Shelving in Progress'', ''Shelved'', ''Shelving Refurbish in Progress'', and ''Shelving Refurbish Done.''<br />
* Modem ID - Shows the Modem ID. (This is hidden by default but can be revealed by right-clicking a column and selecting the "Columns" drop down menu.). <br />
<br />
For the Show WCU history option to be available only a single WCU can be selected.<br />
<br />
'''Trigger upload now'''<br />
<br />
Momentarily stop the WCU, offload it and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger reboot now'''<br />
<br />
Reboots the trigger and WCU. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger collect and upload'''<br />
<br />
This action will cause the task to momentarily stop and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.45.<br />
<br />
'''Trigger VIN readout'''<br />
<br />
Trigger VIN readout, this action will cause the task to momentarily stop .This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.65.<br />
<br />
==New task==<br />
To create a new task for all selected WCUs, click the button [[New task|New Task]]. To learn more about creating each specific task see [[Creating a Task]].<br />
<br />
== Upload Vehicle pins ==<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><VIN>;<ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>WICE_VIN_1;1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will save the pin AA:BB:CC:DD:EE for the ECU 0x1D0D (i.e. HIA) with service area 0x5 and will be associated with the vehicle WICE_VIN_1.<br />
<br />
==Show the Vehicle Position==<br />
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in. <br />
<br />
If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]]. <br />
<br />
==View Diagnostic Trouble Codes==<br />
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]<br />
<br />
If an SoH task has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle. <br />
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.<br />
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".<br />
<br />
==View ECU software==<br />
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]<br />
It is possible to see the ECU software number for each ECU in a vehicle.<br />
Press the button “ECU SW” after you have selected one vehicle. The following view will be<br />
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with<br />
when it was read. You can download the list as a tab-separated text file if you press “Download”.<br />
<br />
==Get WCU Up-time==<br />
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]<br />
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.<br />
<br />
Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.<br />
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.<br />
<br />
From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].<br />
<br />
==Export SoH Data==<br />
[[File:Soh data export.png|frame|SoH Data Export Panel]]<br />
You can export data from SoH tasks to your local computer by using the function<br />
“Export SoH data”. Select the cars you are interested in as you can export for more than<br />
one car in one export.<br />
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage, storage usage and diagnostic trouble codes. <br />
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.<br />
<br />
==Resource Groups==<br />
WCUs and cars can collectively be referred to as "resources". As such they can be grouped<br />
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only<br />
one type of resource is in a resource group.<br />
<br />
You identify a resource group by a gray arrow like icon to the left in the table row. If you<br />
click the icon the entry opens up and makes room for showing which resources are part<br />
of the resource group.<br />
<br />
From version 2.42 viewing the resource group's resources has been improved. More info can be found in [[Resource group's resources]].<br />
<br />
When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a<br />
resource group or not. If you select a resource group, the new task will be downloaded to all the WCUs that are part of the resource group.<br />
As a regular user you can not create and remove resource groups, only an administrator<br />
of the portal can do this.<br />
<br />
From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.<br />
<br />
This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.<br />
<br />
Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".<br />
<br />
==Modules==<br />
If you have the right permission you will be able to view a WCU:s modules, and<br />
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:<br />
<br />
* [[The Portal Administrator View#configure the area5 module|Area5]]<br />
* [[The Portal Administrator View#Configure the audio module|Audio]]<br />
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]<br />
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]<br />
* [[DLT Module|DLT]]<br />
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]<br />
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]<br />
* [[The Portal Administrator View#Configure the File fetcher module|File Fetcher]]<br />
* [[The Portal Administrator View#Configure the GPS Module|GPS]]<br />
* [[The Portal Administrator View#Configure the IDC Module|IDC]]<br />
* [[The Portal Administrator View#Configure the IPEmotion RT Module|IPEmotion RT]]<br />
* [[The Portal Administrator View#Configure the LPD Module|LPD]]<br />
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]<br />
* [[The Portal Administrator View#Configure the M-log Module|M-log]]<br />
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]<br />
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]<br />
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]<br />
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]<br />
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]<br />
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]<br />
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]<br />
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]<br />
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]<br />
* [[The Portal Administrator View#Configure the Video Module|Video]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicles&diff=4007Vehicles2025-08-28T11:47:59Z<p>Robin.karhu: /* Right click context menu */</p>
<hr />
<div><includeonly>=Vehicles Tab=</includeonly><br />
This view is used to handle the various vehicles that are assigned to you. A figure of this view<br />
is presented below in the Figure "Vehicles Tab". At the top, the red section, is a search area where you<br />
type in the criteria to be used for fetching the vehicles you are interested in. As you enter your<br />
criteria a row count is presented in the upper right area to show how many potential matches<br />
there are. The entries are also fetched as you type but only as many rows as fit your current<br />
view are fetched. As you scroll down more results will be fetched.<br />
<br />
[[File:Illustration26.png|none|thumb|700x700px|Vehicles Tab]]<br />
<br />
The number of possible columns to show is quite large. You can select which columns you wish to see by right clicking on the column header and select "Columns..". A small window will pop-up, in which you can select which columns should be visible in the table. These are the available columns:<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
|'''Active alarms'''<br />
|Presents a numeric summary of alarms. It displays the amount of errors and warnings.<br />
|-<br />
| style="font-weight: bold;" | <span id="Connected">Connected</span><br />
| Shows how many minutes have passed since the WCU made a connection to the WICE portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Distance">Distance</span><br />
| Shows the distance the car has been driven the last week. (SoH task specific)<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_DRO">Last DRO</span><br />
| Says when the DRO log file was last transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Last_log">Last log</span><br />
| Shows when the last log file was transferred to the portal.<br />
|-<br />
| style="font-weight: bold;" | <span id="Mileage">Mileage</span><br />
| The column shows the mileage of the car.<br />
|-<br />
| style="font-weight: bold;" | <span id="Plate_number">Plate number</span><br />
| The plate number of the car where the WCU is mounted.<br />
|-<br />
|'''Platform type'''<br />
|Search WCU by platform type.<br />
|-<br />
| style="font-weight: bold;" | <span id="Project_Id">Project Id</span><br />
| Shows the project identification number.<br />
|-<br />
| style="font-weight: bold;" | <span id="Proto_number">Proto number</span><br />
| Shows the proto number.<br />
|-<br />
|'''Resource group'''<br />
|The resource group (if any) the WCU is part of.<br />
|-<br />
| style="font-weight: bold;" | <span id="Series">Series</span><br />
| Shows the series attribute.<br />
|-<br />
| style="font-weight: bold;" | <span id="TSU">TSU</span><br />
| Shows the TSU identifier.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload">Upload</span><br />
| This column says how much data has been transferred from the WCU to the portal the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_date">Upload date</span><br />
| Contains which date the last upload was done<br />
|-<br />
| style="font-weight: bold;" | <span id="Upload_size">Upload size</span><br />
| Says what the size, in kilobytes, of the last data upload was.<br />
|-<br />
| style="font-weight: bold;" | <span id="Up-time">Uptime</span><br />
| Shows how many hours the WCU been running the last week.<br />
|-<br />
| style="font-weight: bold;" | <span id="VIN">VIN</span><br />
| Shows the Vehicle Identification Number of the car where the WCU is mounted.<br />
|-<br />
| style="font-weight: bold;" | <span id="Voltage">Voltage </span><br />
| The column shows the latest known battery voltage as reported by the CEM.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_ID">WCU ID</span><br />
| The MAC ID of the WCU. For example: AA-01-AA-01-AA-01.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Description">WCU Description</span><br />
| A textual comment attached to the WCU.<br />
|-<br />
|'''WCU Firmware'''<br />
|Shows which firmware the WCU uses.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_voltage">WCU voltage</span><br />
| Shows the voltage as measured by the WCU.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_Version">WCU Version</span><br />
| Shows which version the current WCU software has.<br />
|-<br />
| style="font-weight: bold;" | <span id="WCU_storage_usage">WCU storage usage</span><br />
| Shows the amount of storage available to store data on the WCU.<br />
|-<br />
|'''WCU name'''<br />
|Shows the name of the WCU.<br />
|-<br />
|'''WCU state'''<br />
|Shows the current state of the WCU.<br />
|}<br />
<br />
Now, as there are so many columns present you have the option of selecting which ones you would like to see by right-clicking on the table header. If you would like your selection to be remembered between sessions, use the binocular icon with an add sign in bottom right corner in the Figure "Vehicles Tab". To save the currently entered search expression, similarly use the magnifying glass icon with an add sign. To read more about the view and search functionality, click [[Save View and Search Expressions|here]].<br />
<br />
There is a concept called “resource groups” you should be aware of in this panel. A resource group is simply a way to refer to a group of resources (WCU, Car) collectively. An example is when creating tasks you can select a resource group instead of the individual WCU:s to start a new task. Also, when showing the positions on a map, you select a resource group and press “Show position”, all WCU:s in that resource group will show. To see which resources are in a resource group you press the triangle to the left of the row and the row<br />
opens up to show the individual members. To show the members in the view you can rightclick the entry and select the option “find members” from the menu.<br />
<br />
When selecting a row in the table the selected row changes to a blue shade. You can modify<br />
the description of the WCU by clicking in the “Edit Description” button and entering a new description. You can search among the vehicles log files by clicking the “Get log files” button.<br />
<br />
== Right click context menu ==<br />
If you select one or more rows in the table, you can right click on the selected rows. This will display a context menu with several options, some of which are described here.<br />
<br />
''' Go to Tasks Panel ''' <br> <br />
This allows you to instantly jump to the tasks panel, which will automatically perform a search based on either the WCU or the car which the selected row represents.<br />
<br />
''' Go to Search Panel ''' <br><br />
This allows you to instantly jump to the search panel. The search panel will automatically perform a search based on either the WCU or the car.<br />
<br />
''' Go to Timeline ''' <br><br />
This allows you to jump to the Timeline-view, which will adjust itself to the WCU you have selected.<br />
<br />
''' Go to alarms ''' <br><br />
Selecting this will take you to the alarms panel, where a search is conducted for all selected WCUs. This allows you to quickly see all alarms for a specific set of WCU resources. This works well together with the Active Alarms column (which you can read about further up this page), which tells you if a WCU has any active alarms. If a WCU has any active alarms, then using "go to alarms" will allow you to review those alarms in detail.<br />
<br />
'''Upload vehicle pins'''<br />
<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will upload the pin AA:BB:CC:DD:EE for an ECU 0x1D0D (i.e. HIA) with service area 0x5. This PIN will then be associated to the vehicle connected to the WCU.<br />
<br />
'''Compare WCU configurations'''<br />
<br />
Selecting this on a individual WCU will open a dialog where you may choose other WCUs to compare against the selected WCU. Once compared, the result panel that is opened will show only the differing configuration variables for the WCUs.<br />
<br />
''' Remove WCU(s) from Resource Group ''' <br><br />
If WCUs which are included in a resource group are selected, the menu option "Remove WCU(s) from Resource Group" will appear. They do not have to be in the same resource group as each other. If a resource which do not fulfill this requirement is selected in addition, this option will not be visible.<br />
<br />
'''Show WCU history'''<br />
[[File:ShowWCUHistoryUpdatedAgain.png|alt=|thumb|Example of a Show WCU history]]<br />
Selecting this shows a window with the history of the selected WCU. The following columns will be displayed in the window:<br />
<br />
* Change date - Displays the date the WCU was changed.<br />
*Type of change- Displays whether the update involved a configuration change, a tools change, or a label change.<br />
* Description - Displays a description of the WCU.<br />
* Active - Shows if the WCU is active or not.<br />
* WCU ID - Shows the WCU ID.<br />
* WCU name - Displays the WCU name.<br />
* WCU version - The WCU version.<br />
* WCU firmware version - The WCU firmware version.<br />
* Changed by - The user who modified the WCU.<br />
* Resource group - The resource group.<br />
* ICCID - The SIM card installed.<br />
*State - reflects the WCU’s status at the time of the change. Possible states include: ''In Operation'', ''Shelving in Progress'', ''Shelved'', ''Shelving Refurbish in Progress'', and ''Shelving Refurbish Done.''<br />
* Modem ID - Shows the Modem ID. (This is hidden by default but can be revealed by right-clicking a column and selecting the "Columns" drop down menu.). <br />
<br />
For the Show WCU history option to be available only a single WCU can be selected.<br />
<br />
'''Trigger upload now'''<br />
<br />
Momentarily stop the WCU, offload it and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger reboot now'''<br />
<br />
Reboots the trigger and WCU. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.39<br />
<br />
'''Trigger collect and upload'''<br />
<br />
This action will cause the task to momentarily stop and upload any data as soon as possible. This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.45.<br />
<br />
'''Trigger VIN readout'''<br />
<br />
Trigger VIN readout, this action will cause the task to momentarily stop .This trigger button is only visible if the WCU state is in-operation and the WCU version is later then 2.65.<br />
<br />
==New task==<br />
To create a new task for all selected WCUs, click the button [[New task|New Task]]. To learn more about creating each specific task see [[Creating a Task]].<br />
<br />
== Upload Vehicle pins ==<br />
Selecting this will open a window where you may select a file to upload vehicle PINs. The expected structure of the file is one line per PIN where each line is of the format <code><VIN>;<ECU-ID (hexadecimal)>;<ECU name>;<Service Area (hexadecimal)>;<PIN></code>.<br />
<br />
For example: <code>WICE_VIN_1;1D0D;HIA;0x5;AA:BB:CC:DD:EE</code> will save the pin AA:BB:CC:DD:EE for the ECU 0x1D0D (i.e. HIA) with service area 0x5 and will be associated with the vehicle WICE_VIN_1.<br />
<br />
==Show the Vehicle Position==<br />
To see the last reported position of a vehicle, click the “Show Position” button which opens up a map view of where the vehicle was last known to be. You can view several vehicles simultaneously by ctrl- or shift-clicking the vehicles you are interested in. <br />
<br />
If you want to know more about the "Show position"-tool [[Show position|you can read more about it here]]. <br />
<br />
==View Diagnostic Trouble Codes==<br />
[[File:Illustration28.png|thumb|300px|Viewing Diagnostic Trouble Codes]]<br />
<br />
If an SoH task has been enabled to do Diagnostic Trouble Code (DTC) read-outs, you can view the trouble codes by selecting the vehicle you are interested in and push the button “View DTCs”. In Figure "Viewing Diagnostic Trouble Codes" you can see an example presentation of DTCs. There are five columns in the table. The leftmost is the name of the ECU issuing the DTC, next is the date and time when the trouble code was read-out, the actual DTC with clear text description, and thereafter the VIN and WCU id of the vehicle. <br />
If you click in the column for the actual trouble code, a dialog opens with that particular trouble codes. You can extend the size of the dialog in order to examine the trouble codes in more detail.<br />
You can also search the trouble codes as you can see at the top of Figure "Viewing Diagnostic Trouble Codes".<br />
<br />
==View ECU software==<br />
[[File:Illustration29.png|thumb|300px|ECU Software Versions]]<br />
It is possible to see the ECU software number for each ECU in a vehicle.<br />
Press the button “ECU SW” after you have selected one vehicle. The following view will be<br />
shown. As you can see in Figure "ECU Software Versions", each ECU's software number is shown along with<br />
when it was read. You can download the list as a tab-separated text file if you press “Download”.<br />
<br />
==Get WCU Up-time==<br />
[[File:Wcu_uptime.png|frame|WCU Up-time Dialog]]<br />
This function is used to get a compilation of the up-time of a set of vehicles during a particular time span. Select the WCUs you are interested in and the click the “Get WCU uptime” button. This brings up the dialog to the right.<br />
<br />
Choose the dates you are interested by choosing a start and end date. Next you have the option of downloading a CSV file, or excel file. The up-time in that file is listed as hours up-time per day per WCU.<br />
The other option is to compile the up-time in a chart shown on screen. The up-time is averaged over the WCUs selected for each day. WCUs having no up-time at all are excluded from the compilation.<br />
<br />
From version 2.42 there is a new feature to display the WCUs uptime based on the data sent from statusd. More info in [[WCU Uptime]].<br />
<br />
==Export SoH Data==<br />
[[File:Soh data export.png|frame|SoH Data Export Panel]]<br />
You can export data from SoH tasks to your local computer by using the function<br />
“Export SoH data”. Select the cars you are interested in as you can export for more than<br />
one car in one export.<br />
You select the dates you are interested in getting the data from. Check each item you are interested in. Currently you can select mileage, WCU voltage, ECU software versions, battery voltage, storage usage and diagnostic trouble codes. <br />
The file can be exported in CSV format (suitable for Excel and other spreadsheet applications) and in XML format.<br />
<br />
==Resource Groups==<br />
WCUs and cars can collectively be referred to as "resources". As such they can be grouped<br />
together and be handled collectively in order to ease the administration of a set of similar individuals. A resource group can consist of both cars and WCUs but usually only<br />
one type of resource is in a resource group.<br />
<br />
You identify a resource group by a gray arrow like icon to the left in the table row. If you<br />
click the icon the entry opens up and makes room for showing which resources are part<br />
of the resource group.<br />
<br />
From version 2.42 viewing the resource group's resources has been improved. More info can be found in [[Resource group's resources]].<br />
<br />
When a new task is created any resource groups assigned to you will show up in addition to individual WCUs. There is, however, no indication as to the particular entry is a<br />
resource group or not. If you select a resource group, the new task will be downloaded to all the WCUs that are part of the resource group.<br />
As a regular user you can not create and remove resource groups, only an administrator<br />
of the portal can do this.<br />
<br />
From version 2.42 of the portal it is easier to search out members of resource groups using the "Resource group" column. When searching in this column one will get results that either matches the name of a resource group WCU or WCUs that are part of a resource group that matches the search criteria. In other words, if we search for "ABCD" we will get the resource group "ABCD" together with all WCUs that are part of the "ABCD" group.<br />
<br />
This column can also be used to list all WCUs that are not part of any resource group. To perform this search, put "^$" in the "Resource group" column.<br />
<br />
Alternatively, you can find the resource group that a WCU belongs to, by right-clicking the WCU and select "Search resource group".<br />
<br />
==Modules==<br />
If you have the right permission you will be able to view a WCU:s modules, and<br />
configure them. A module is a specific functionality of the WCU, such as a measurement tool. The available modules are:<br />
<br />
* [[The Portal Administrator View#configure the area5 module|Area5]]<br />
* [[The Portal Administrator View#Configure the audio module|Audio]]<br />
* [[The Portal Administrator View#Configure the Blue piraT Module|Blue piraT]]<br />
* [[The Portal Administrator View#Configure the Canrecorder Module|Canrecorder]]<br />
* [[DLT Module|DLT]]<br />
* [[The Portal Administrator View#Configure the DoIP Module|DoIP]]<br />
* [[The Portal Administrator View#Configure the ETAS Module|ETAS]]<br />
* [[The Portal Administrator View#Configure the File fetcher module|File Fetcher]]<br />
* [[The Portal Administrator View#Configure the GPS Module|GPS]]<br />
* [[The Portal Administrator View#Configure the IDC Module|IDC]]<br />
* [[The Portal Administrator View#Configure the IPEmotion RT Module|IPEmotion RT]]<br />
* [[The Portal Administrator View#Configure the LPD Module|LPD]]<br />
* [[The Portal Administrator View#Configure the MCD-Hub Module|MCD-Hub]]<br />
* [[The Portal Administrator View#Configure the M-log Module|M-log]]<br />
* [[The Portal Administrator View#Configure the MQTT Module|MQTT]]<br />
* [[The Portal Administrator View#Configure the RP Module|Rapid Prototyping (RP)]]<br />
* [[The Portal Administrator View#Configure the Signal Reader Module|Signal Reader]]<br />
* [[The Portal Administrator View#Configure the SmartEye Module|Smart Eye]]<br />
* [[The Portal Administrator View#Configure the Soft-Hub|SoftHub]]<br />
* [[The Portal Administrator View#Configure the Software Download Module|Software Download (SWDL)]]<br />
* [[The Portal Administrator View#Configure the State of Health Module|State of Health (SoH)]]<br />
* [[The Portal Administrator View#Configure the Uptime Module|Uptime]]<br />
* [[The Portal Administrator View#Configure the Vinreader Module|Vinreader]]<br />
* [[The Portal Administrator View#Configure the Video Module|Video]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.95&diff=4004New features in v2.952025-08-28T11:45:12Z<p>Robin.karhu: </p>
<hr />
<div>== Improved support for uploading a vehicle import file ==<br />
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.<br />
<br />
== DLT tasks for strict resource groups ==<br />
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]]. Read more about uploading PINs [[Vehicles#Upload Vehicle pins|here]].<br />
<br />
== Compare WCU configurations ==<br />
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]<br />
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]<br />
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]<br />
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the [[Vehicles#Right click context menu|right-click menu]] on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.95&diff=4003New features in v2.952025-08-28T11:42:00Z<p>Robin.karhu: /* DLT tasks for strict resource groups */</p>
<hr />
<div>== Improved support for uploading a vehicle import file ==<br />
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.<br />
<br />
== DLT tasks for strict resource groups ==<br />
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]]. Read more about uploading PINs [[Vehicles#Upload Vehicle pins|here]].<br />
<br />
== Compare WCU configurations ==<br />
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]<br />
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]<br />
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]<br />
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the right-click menu on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Creating_a_Task&diff=4002Creating a Task2025-08-28T11:36:09Z<p>Robin.karhu: /* DLT UDS Mode */</p>
<hr />
<div><includeonly>== Creating a Task==</includeonly><br />
You create a new task by pressing the "New Task" button on the bottom of the "Tasks" tab. This will open a window where you choose the type of task you want to create. Note that it is not possible to create a new task for a WCU which has the system labels <nowiki>''</nowiki>shelving_in_progress<nowiki>''</nowiki> or <nowiki>''</nowiki>shelving_done<nowiki>''</nowiki>. However, if the WCU has the latter label, it is possible to unshelve it using the corresponding button in the bottom of the Vehicle-tab. Here we will go through how to create tasks of each of the different kinds of 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. <br />
<br />
To learn about how to add resources to the task, check [[New task|here]].<br />
<br />
== Arcos ==<br />
[[File:Arcos-task.png|alt=The dialog for creating an Arcos task.|thumb|The dialog for creating an Arcos task.]]<br />
The WICE system can interact with external loggers as well. From version 2.71 the portal can interact with the Arcos-logger from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.ccmc''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.<br />
<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the Arcos - no upload will be required.<br />
<br />
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]]).<br />
<br />
== Area5 ==<br />
[[File:Area5 new task.png|thumb|500x500px|Area5 task]]<br />
Area5 tasks are used to read out data from the memory of ECUs. <br />
<br />
'''Assignment:''' To create a new Area5 task you first have to create an Area5 assignment in the [[Area5 Assignment Editor|Area5 Assignment Editor]]. <br />
<br />
'''Validate ECU SW version on WCU:''' By checking this box, the WCU will validate that the ECU SW version of the task and the actual ECU are the same before starting the task. If they are different, it will not start the task.<br />
<br />
'''Trigger Expression:''' The task can be started by an expression. This option lets the user specify start trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). For an explanation of trigger conditions look [[Server Trigger|here]].<br />
<br />
'''Sync Signal:''' It is possible to specify a signal with given values that will be sent when the Area5 task starts and stops. This can be used to synchronize the Area5 read-out with external measurements systems like the M-Log.<br />
<br />
== Audio ==<br />
An audio task makes it possible to record audio from a connected microphone. An audio recording can be started in five ways:<br />
* '''Trigger button''': to initiate the recording you need to attach a button to the WCU in order to start in the audio recording.<br />
* '''Signal reader''': initiate the recording by a trigger expression in a Signal Reader assignment. The recording is started as soon as a Signal Reader '''recorder''' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the audio recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Audio_Device_n internal signal will be selected. <br />
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of triggers look [[Server Trigger|here]].<br />
* '''Audio level''': Start the trigger once the microphone registers volume above a certain threshold.<br />
* '''None''': start the recording as soon as possible.<br />
<br />
In addition to this, you can set the '''pre-trig''' time which is only valid in the cases of trigger button, signal reader, expression and audio level above. As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the audio has already been recorded for the number of seconds specified. This can be handy when you press the trigger button to make a comment about an event where the event was audible.[[File:Skärmavbild 2019-12-18 kl. 14.28.52.png|alt=Audio task|thumb|Audio task]]A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.<br />
It is possible to monitor the audio live. To do this, check the box "Monitoring". To listen to the live audio you should use a tool such as [http://confero.alkit.se Alkit Confero]. <br />
<br />
There is more information about audio in WICE [[Wice audio|here]].<br />
<br />
Audio tasks can be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
== Blue piraT ==<br />
The blue PiraT is a measurement system from Telemotive AG that can be configured with measurement set-ups, and data accessed through the WICE Portal. Note that to use the blue PiraT module, the WCUs to be used need to be preconfigured with a special software package (i.e. an "extra bundle"). Contact Alkit Communications in order to set this up.<br />
<br />
== CAN-recorder ==<br />
[[File:Canrecorder.png|thumb|Canrecorder]]<br />
Canrecorder is a measurement module that allows CAN frames to be captured and logged.<br />
<br />
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.<br />
<br />
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”<br />
<br />
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. <br />
<br />
===Scheduling=== <br />
<br />
For WCUs with version >= 2.53 this task can be scheduled by selecting the "Add schedule"-checkbox. By doing so, the panel shown in Figure "Schedule Panel" appears. By thereafter selecting the "ASAP" checkbox, the task will be performed once and as soon as possible. If instead the task is to be performed at a specified time, deselect the "Time span" and "Repeat"-checkboxes and select the sought time in the "Start field". The task can also be performed within a certain time span, and in this case "Time span" should be checked and the Date in "End" field specified. Repetition of the task is defined by checking the "Repeat" checkbox, defining a interval size in the field after "Every" and a recurrence rate in the drop down menu. The task will then be repeated at this rate until the date defined in the "Until" field is reached. By selecting the "On ignition" checkbox, the task will be performed once on ignition. If delay is above 0 then the task will be performed once the configured amount of seconds have passed after ignition.<br />
<br />
[[File:Illustration Schedule.png|thumb|left|600px|Schedule Panel]]<br />
[[File:Scheduling on ignition.png|thumb|300x300px|Schedule Panel with 'On ignition' enabled]]<br />
<br clear="all"><br />
<br />
To control the time zone in which the task scheduling is to be performed the "WCU local time"-checkbox is used. If this option is deselected, the task will be performed in UTC-time (the date fields present the portal local time). On the other hand, if this box is checked, the task will be performed according to the local time zone predefined for the WCU. A WCU time zone can be defined for a WCU with version >= 2.53 by an administrator using "Edit configuration" in the [[The Portal Administrator View#The Vehicles Tab|Vehicles panel]]. This is useful when there is a need to perform a certain task at a specific time of the day regardless of which country the vehicle is in. For instance, when selecting 100 different WCUs scheduled to perform a task at 10:00, checking the "WCU local time"-checkbox will result in them performing the task according to their time zone setting. Without checking this option, the task will be performed in the corresponding UTC-time, which could mean in the middle of the day or night depending on where the vehicle is located.<br />
<br />
== Diagnostic Log and Trace (DLT) ==<br />
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. From version 2.92.0 the latter is also supported. You switch between the using the button "DLT UDS mode". <br />
<br />
=== DLT Daemon Mode ===<br />
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]. <br />
[[File:New-dlt-daemon.png|thumb|The DLT new task dialog for the daemon mode.]]<br />
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. <br />
<br />
So when creating a DLT task on WCUs with software version 2.72.0 or later the number of daemons can be specified and for each daemon the following needs to be specified:<br />
<br />
# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon.<br />
# Daemon port - which port on the address the daemon is at.<br />
# 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].<br />
<br />
==== Older WCUs ====<br />
For WCUs with software version earlier than 2.72.0 only one daemon is supported and only filters can be configured when creating a DLT task. To specify the daemon address and port go to the [[DLT Module]] instead.<br />
<br />
=== DLT UDS Mode ===<br />
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 "Add transfer". An editable row shows up in the table where you can enter data. Enter the ECU ID as hexadecimal number, an optional pin code (more on this later) and the directory to fetch. You can add as many entries as you wish.<br />
[[File:Dlt-uds-task.png|thumb|DLT UDS service 38 task]]<br />
There is a check box with the text "Use vehicle specific PINs". By checking the box, the system will try to get a vehicle specific PIN code for each ECU and WCU. The type of PIN for this service is area 19. How to supply the system with such PIN codes is described [[Vehicles#Upload Vehicle pins|here]].<br />
<br />
There is also a button "Check PINs" available to resource groups that will—if the above check box is checked—look for any missing PINs in the portal for the configured ECUs.<br />
<br />
== ETAS ==<br />
Through an ETAS task, an ETAS ES720 Drive Recorder system can be configured, and measurement data offloaded and accessed through the WICE Portal.<br />
<br />
When creating an ETAS task, the task description file you select must be a .exp file.<br />
<br />
== Ethernet capture ==<br />
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]].<br />
<br />
== File fetcher ==<br />
[[File:File fetcher proxy example.png|thumb|The new task dialog of the File fetcher task.]]<br />
The File fetcher task fetches files from a specified unit and makes them available for downloading in the Portal.<br />
<br />
The following needs to be specified when creating such a task:<br />
<br />
* '''File path''' - One or several paths to a files or file-containing directories on the unit's file system. This specifies which files that will be fetched.<br />
* '''Username''' - To log in to the unit.<br />
* '''Password''' - To log in to the unit.<br />
* '''IP address''' - To find the unit.<br />
* '''Port''' - To find the unit. Default is 22, but can be changed.<br />
<br />
Furthermore, the task also allows the use of a proxy.<br />
<br />
To use a proxy, the '''Use Proxy''' checkbox has to be checked, and the following must be specified:<br />
<br />
* '''Proxy Username''' - To log in to the proxy unit.<br />
* '''Proxy Password''' - To log in to the proxy unit.<br />
* '''Proxy IP Address''' - To find the proxy unit.<br />
* '''Proxy Port''' - To find the proxy unit. Default is 22, but can be changed.<br /><br />
== IDC ==<br />
The Internal Diagnostic Client (IDC) is a measurement module that allows a sequence of diagnostic requests to be sent and responses recorded. The sequence of diagnostic requests can be created as an assignment in the Assignment tab, alternatively can be uploaded to the portal as a text file (usually ending with ".seq"). This task can also be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
== IPEmotion RT ==<br />
The WICE system can interact with external loggers as well. From version 2.72 the portal can interact with the logger IPEmotion RT from Ipetronik. You create your measure task using an external tool which creates a file which you can upload for this type of task. The file should have the extension "''.irf''". When the task is downloaded the WICE system will then forward this file to the external logger. The WICE system can also take care of uploading the result files as well where you can retrieve the files using this portal.<br />
<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the IPEmotion RT - no upload will be required.<br />
<br />
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]]).<br />
<br />
== LPD ==<br />
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.<br />
[[File:Screenshot from 2023-05-24 16-09-55.png|thumb|View an LPD task]]<br />
[[File:Screenshot-edit-lpd.png|thumb|Upload opportunity after pressing the Edit button]]<br />
From version 2.83.0 of the WICE portal the task measurement file can be updated via the View Task function in the Tasks tab and a dialog as shown to the right will appear. By pressing the "Edit" button in the lower right corner, you will be presented with the possibility to upload a new measurement task file. This is shown with a red triangle in the illustration on the right.<br />
<br />
== M-Log ==<br />
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]]<br />
[[File:Screenshot from 2022-04-21 09-34-11.png|alt=Entering ECU software version|thumb|Entering ECU software version]]<br />
Select the "Use existing measurement configuration" checkbox if a measurement setup file already exists on the MLOG - no upload will be required.<br />
<br />
==== Software version validation (Available from version 2.74.0) ====<br />
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. <br />
<br />
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 "Add" button. The data you just entered will be added to the table and evaluated against what the WICE system has read out from the vehicle. In the example to the right something is incorrect which is indicated by the yellow color. To see the exact reason, simply use the cursor to see the specific message. <br />
<br />
A negative validation in not enforced in the sense that you cannot run the assignment but rather an indication that it might not work as expected. You can always go ahead and press "Submit". <br />
<br />
== MQTT ==<br />
A MQTT task makes it possible to record data from a MQTT message broker, by specifying a specific topic.<br />
<br />
== Rapid prototyping ==<br />
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]].<br />
[[File:Rapid prototyping task.png|thumb|Rapid prototyping task]]<br />
The rapid prototyping tab can be seen in Figure "Rapid prototyping task". <br />
<br />
An RP task must consist of at least an 'RP binary' or a 'Web application zip file'.<br />
<br />
== SoftHub ==<br />
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.<br />
<br />
When creating a SoftHub task, you select a .shub task file, and then proceed in the same way as the Signal Reader task. <br />
<br />
The SoftHub task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''server triggers''' to the task that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].<br />
<br />
== Signal Reader == <br />
[[File:Illustration SignalReader.png|thumb|271x271px|Signal reader task]]<br />
Signal Reader is a data capture module that allows monitoring and logging of CAN and FlexRay signals, as well as diagnostics data, and ECU-internal signals read by CCP or XCP. To create a Signal Reader task you proceed as follows:<br />
<br />
1. You either select an assignment file of .haf format, or choose an assignment created in the assignment creator (see [[Signal Reader Assignment Wizard]]). Your current choice will be displayed in the "Chosen file" field.<br />
<br />
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]].<br />
<br />
3. With a Signal Reader task you can monitor CAN, FlexRay, ODB-II and WCU-internal signals live by selecting "Monitor signals". When selected, two boxes will appear under the task description. In the left one you search for signals and drag them over to the right one where the signals to be monitored are listed. You can later see the monitored signals by pressing the '''Monitor Signals''' button either in the Tasks tab or in the Vehicles tab. It is also possible to copy the signals text in the bottom right corner of the right box. Next to the copy text button you can also paste signals as text where the pasted signal names will be matched against the list of unselected signals<br />
<br />
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).<br />
<br />
5. The Signal Reader task will generate result files. It may be interesting to know if certain signals reach certain values in these result files, therefore it is possible to add '''Server Triggers''' to the assignment that will trigger and add a suitable label to the corresponding result file. Read more about this [[Server Trigger|here]].<br />
<br />
A Signal reader task can be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
=== The Signal Broker === <br />
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]].<br />
<br />
=== Files containing references to sequence files === <br />
[[File:SequenceFileForSignalreader.png|thumb|right|Sequence Files References in .haf File]] <br />
If the measurement file contains references to sequence files, you are also required to select these in order to run the task. The portal scans the .haf file for such entries and presents this to you, see illustration 4.2. Click the button for each sequence file reference to upload each sequence file needed. Some requests in the sequence file may be for reading DTCs, and in such cases you can select the option of also reading associated ''Snapshots'' or ''Extended data''. An example of this can found in Figure "Sequence Files References in .haf File". <br />
[[File:SequenceFilesForSignalreaderWithFunctionalQuery.png|thumb|right|Sequence File with Functional Query]] <br />
<br />
Here, the .haf file contained two references to sequence files. As no sequence files have yet been uploaded, the selection for reading snapshot or extended data is grayed out. In Figure "Sequence File with Functional Query" we have selected one such sequence file containing (functional) DTC requests. Here we have checked that we would like to read ''Extended data''. It is also possible to select both ''Snapshots'' and ''Extended data''. <br />
<br><br />
<br />
=== WICE internal signals ===<br />
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]]<br />
<br />
== SoH ==<br />
[[File:Screenshot from 2021-04-01 09-43-34.png|thumb|799x799px|SoH]]<br />
A State of Health (SoH) task collects specific status information from vehicles. You select which information you want the task to collect by filling in one or more of the checkboxes shown in Figure "SoH". The number of checkboxes shown can vary depending on the WICE installation. In order for SoH data to be correctly interpreted, relevant description files (e.g. SDDB) for the vehicles executing the SoH task may have to been available. To add such a description file for a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog|The Edit Car Dialog]].The six different options are:<br />
*Mileage<br />
*Voltage<br />
*Read ECU software numbers<br />
*Read ECU DTC:s (optionally including 'Snapshot' and 'Extended data')<br />
*Read OBD-II PIDs<br />
*App Diagnotstic Db Part Num<br />
*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939|j1939 protocol]]<br />
*Odometer, reading the odometer using the [[wikipedia:SAE_J1939|j1939 protocol]] (available from WCU version 2.63)<br />
*Clear DTCs. <br />
**If reading DTCs is requested as well, those will be read before clearing the DTCs. (available from WCU version 2.63)<br />
**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)<br />
*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 'engine_hours' (as default, can be changed on a customer basis). This label shows the latest read value and is available on the vehicle. <br />
<br />
This task can also be scheduled in the same manner as described for the Canrecoder task.<br />
<br />
Some selections above might not be available to you as this is a configuration setting depending on customer.<br />
<br />
== SWDL ==<br />
[[File:Swdl task Screenshot from 2023-06-28 14-50-55.png|thumb|791x791px|New SWDL task]]<br />
A Software Download (SWDL) task updates the ECU software in one or more ECUs in one or more vehicles. A number of Versatile Binary Format (VBF) files containing the ECU software need to be supplied, along with PIN codes to allow security access to re-program the ECUs. The PIN codes should be in the format of five hexadecimal numbers, e.g. <code>ff:00:1a:2c:77</code> (or alternatively, omitting the colon separator, <code>ff001a2c77</code>). When a SWDL task has been created and assigned to one or more WCUs, it will cause all vbf files to be downloaded to the WCUs, and then the actual re-programming can be triggered by the vehicle user through the WCU status GUI web interface. The uploaded vbf-files are presented in a table along with its ECU and software part type (SW part type). In a separate table, the PIN codes for each ECU are presented along with the total number of files uploaded per WCU, see Figure "New SWDL task". To get an overview of how the files relate to the ECUs it is possible to choose the "Group by"-option when right clicking the ECU column in the file table. <br />
<br />
SWDL tasks can optionally include a '''pre-update sequence file and/or a post-update sequence file'''. The diagnostic requests of those sequence files will be sent before and after the ECU re-programming respectively.<br />
<br />
SWDL tasks can optionally include one '''signature file''' (containing checksums). The file is assumed to be an xml file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)<br />
<br />
SWDL tasks can optionally include a '''VGM unlock''' access control mechanism, with a PIN code for the VGM node. This is specifically for vehicles requiring this kind of access control for ECU re-programming.<br />
<br />
By checking the box '''Run SoH after completion''' it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.<br />
<br />
If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "'''Use Vehicle Pin mappings'''". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes [[The Portal Administrator View#Upload a file describing ECU pin codes for a vehicle|here]].<br />
<br />
SWDL tasks can optionally contain a '''Trigger Expression''' which must be fulfilled within a specified time limit ("Wait time") for ECU re-programming to be allowed. The trigger expression follows the same syntax as Signal Reader trigger expressions (or [[Server Trigger|Server Triggers]], audio/video triggers), and should be built up from signals being measured in a Signal Reader assignment. The user must make sure that there is a Signal Reader assignment on the WCUs of the SWDL task, with the signals of the trigger expression being measured.<br />
<br />
<br />
It is also possible to choose to '''ignore checksums''' and/or '''disable pre-programming''' using the corresponding checkboxes.<br />
<br />
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).<br />
<br />
== Video ==<br />
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:<br />
* '''Trigger button''': To initiate the recording you need to attach a button to the WCU in order to start in the video recording.<br />
* '''Signal reader''': Initiate the recording when a recorder in a Signal Reader assignment starts. The recording is started as soon as a Signal Reader ''recorder'' is started. You specify the name of the Signal Reader recorder (e.g. SREC_0) you want to start the video recording. You can also enter "auto" as the recorder name, in which case a recorder that include the Video_Device_n internal signal will be selected. <br />
* '''Expression''': Similar to the 'Signal reader' trigger option, the 'Expression' option lets the user specify start and stop trigger conditions based on logical expressions containing signals measured by the Signal Reader module. Note that the user must make sure the signals present in the expression are actually measured (otherwise the expression will never be true). Unlike the 'Signal Reader' trigger, there does not have to be a recorder configured in the Signal Reader measurement assignment. For an explanation of how to enter triggers, have a look [[Server Trigger|here]].<br />
* '''None''': start the recording as soon as possible. (Use this with caution, since it tends to produce prohibitively large video files.)<br />
<br />
In addition to this, you can set the '''pre-trig''' time (not valid in the cases of the 'None' trigger option above). As an example, let's assume the trigger button method is selected. At the moment the trigger button is pressed the video has already been recorded for the number of seconds specified.<br />
<br />
A maximum '''duration''' of the recording can also be set, in seconds from the start trigger event. If there is a stop trigger expression specified, the recording will be stopped either when the stop expression is fulfilled or the max duration is passed, whichever occurs first. If you do not enter a duration it will be set to a default value of 120 seconds.<br />
<br />
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.<br />
<br />
Read more about the video support in WICE [[WICE_video|here]].<br />
<br />
== Applicable for all types ==<br />
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]].<br />
<br />
=== Site specific features ===<br />
<br />
==== Announce result file availability ====<br />
[[File:Resultfilepanel.png|thumb|Announced On column]]<br />
If enabled at your site, there might be an opportunity to announce to third party applications that a result file is available using a [[wikipedia:Jakarta_Messaging|JMS API]]. By checking this box, as soon as a result file is added in the back-end this will be signaled using a customer specific event. The check box title is "Announce result file availability", this can be seen in the image in [[#SoH|SoH]]. Starting from version 2.87.0, there's a new 'Announced On' column that keeps track of when the result file was announced.<br />
<br />
==== Retention time ====<br />
[[File:Retention time.png|thumb|435x435px|Retention time]]<br />
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. <br />
<br />
It is possible to set a default retention time for resource groups. To do this, add a global value label named '''RETENTION_TIME''' to the resource group and give it an appropriate value. This value will then be used as a template value when creating a new task for this resource group. If multiple resource groups have this label and they have different values, the one with the lowest/shortest retention time value will be chosen as the template value.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.95&diff=4001New features in v2.952025-08-28T11:20:45Z<p>Robin.karhu: </p>
<hr />
<div>== Improved support for uploading a vehicle import file ==<br />
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.<br />
<br />
== DLT tasks for strict resource groups ==<br />
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]].<br />
<br />
== Compare WCU configurations ==<br />
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]<br />
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]<br />
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]<br />
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the right-click menu on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=New_features_in_v2.95&diff=4000New features in v2.952025-08-28T11:14:36Z<p>Robin.karhu: DLT tasks and Compare WCU configurations</p>
<hr />
<div>== Improved support for uploading a vehicle import file ==<br />
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.<br />
<br />
== DLT tasks for strict resource groups ==<br />
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]].<br />
<br />
== Compare WCU configurations ==<br />
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]<br />
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]<br />
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]<br />
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the right-click menu on a selected WCU in the [[Vehicles|vehicles tab]]. Doing so opens a dialog where you can select multiple other WCUs that will be compared against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs, if there are any.</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:Compare_WCU_configurations_-_result.png&diff=3999File:Compare WCU configurations - result.png2025-08-28T11:11:36Z<p>Robin.karhu: </p>
<hr />
<div>Result panel from comparing WCU configurations</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:Compare_WCU_configurations_-_selections.png&diff=3998File:Compare WCU configurations - selections.png2025-08-28T11:10:22Z<p>Robin.karhu: </p>
<hr />
<div>Lists of unselected and selected WCUs to compare with</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=File:Compare_WCU_configurations_-_menu.png&diff=3996File:Compare WCU configurations - menu.png2025-08-28T11:08:29Z<p>Robin.karhu: </p>
<hr />
<div>Right-click menu</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=I/O_configurations&diff=3970I/O configurations2025-06-13T09:17:43Z<p>Robin.karhu: /* Check PINs */</p>
<hr />
<div><div class="keywords"> io, io configurations, io config, io configs </div><br />
<includeonly>= I/O configurations =</includeonly><br />
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".<br />
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]<br />
<br />
==Edit CAN channels==<br />
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]<br />
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.<br />
<br />
===Channel===<br />
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.<br />
<br />
===Speed (kB)===<br />
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.<br />
<br />
=== FD Speed (kB) ===<br />
[[File:Wcu-configuration-can-fd.png|alt=CAN FD setting for the HMX platform|thumb|CAN FD setting for the HMX platform]]<br />
If the platform is HMX and the WCU version is 2.91.0 or later, a column will appear for the CAN channel. <br />
<br />
===Name===<br />
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.<br />
<br />
===Comment===<br />
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.<br />
<br />
===Add WMU(s)===<br />
If your Portal has [[WMU | WMU's]] enabled the "Add WMU" button will show in the CAN section. You can then add/remove WMU's and configure their CAN channels in the same way as the WCU's CAN channels are configured. For each WMU that is added, a corresponding tab is added under the [[The_Portal_Administrator_View#WMU's_Power_Management | Power Management tab]] for configuring the WMU's power behaviour.<br />
<br />
=== Add CAN channels ===<br />
If your Portal has Vehicle Communication Forwarder enabled, the "Add CAN channels" button will show in the CAN section. If both WMUs and Vehicle Communication Forwarder are enabled in your Portal, only "Add CAN channels" will show up. After having added a Vehicle Communication Forwarder with at least one CAN channel, pressing the button again will add more CAN channels to the Vehicle Communication Forwarder. When removing CAN channels, it is possible to either remove the entire Vehicle Communication Forwarder, or individual CAN channels from it.<br />
<br />
==Edit Ethernet Channels==<br />
[[File:NewEthernetChannel.png|thumb|Edit Ethernet Channels]]<br />
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains eight columns and the individual meaning is as follows.<br />
<br />
===Channel===<br />
This column indicates which interface or interfaces that exists.<br />
<br />
===Addressing mode===<br />
In this column the Addressing mode is configured. The choices are "DHCP client", "AutoIP" and "Static".<br />
<br />
===IP address===<br />
Here you set the static IP address if you have selected "Static" as the Addressing mode.<br />
<br />
===Netmask===<br />
Here you set the netmask if you have selected "Static" as the Addressing mode.<br />
<br />
===Default route===<br />
Here you set the default route if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. The default route is the route that takes effect when no other route is available for an IP destination address.<br />
<br />
===Name Server (DNS)===<br />
Here you set the Name Server if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. Here you set the name of the DNS protocol.<br />
<br />
===Name===<br />
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.<br />
<br />
===Comment===<br />
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.<br />
<br />
==The Miscellaneous Section==<br />
[[File:Screenshot from 2024-09-16 09-49-47.png|thumb|Miscellaneous]]<br />
This section is available for WCUs with version 2.49 or later.<br />
===Set digital out 3 on boot=== <br />
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).<br />
<br />
===Diagnostic tester priority===<br />
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".<br />
<br />
=== Allow ethernet activation on WCU ===<br />
For WCUs of version 2.90.4 or later it is possible to choose whether or not to allow the WCU to use ethernet activation. Not allowing this might disturb some of the WCUs features.<br />
<br />
===Set 5V out on boot===<br />
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.<br />
<br />
===Activate buzzer on detected digital input change===<br />
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.<br />
<br />
=== Diagnostic firewall disable and PIN ===<br />
Option to disable diagnostic firewall. Requires PIN. Visible for WCUs with version 2.89.0 or later.<br />
<br />
==Manage templates==<br />
[[File:Io config2.png|thumb|frame|Selecting Template]]<br />
Admins can save configs as templates (see [[#Manage templates (for admins) | Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.<br />
Clicking "Apply" will apply the selected template. You can always change settings or add more info, the template could be anything you need or just act as a starting point.<br />
<br />
If WMUs are enabled in the portal, a template will save the CANs from each WMU and when a template is selected the WMU CANs are applied 1:1 to each existing WMU in the configuration. <br />
If there are no WMUs in the configuration the template's WMU CANs will not be applied, only the WCU's CANs.<br />
<br />
==Manage templates (for admins)==<br />
[[File:Io config3.png|thumb|frame|Manage Templates (admin view)]]<br />
[[File:Io config4.png|thumb|frame|Manage Templates (with WMUs enabled)]]<br />
If you are an admin you have an extra button "Save current config as template" in the Manage configuration templates window. Clicking it to save the current configuration as a template will prompt you for a name. If the name already exists (case insensitive) a confirmation dialog will popup before overwriting.<br />
<br />
Additionally, as admin you will be able to remove existing templates, which is done by clicking the red "Remove record" icon to the right of the template name. A confirmation dialog will popup to prevent deletion by mistake.<br />
<br />
==Show Vehicle Profile==<br />
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]<br />
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.<br />
<br />
== Check PINs ==<br />
Requires version 2.89.0 or later. Pressing '''Check PINs''' for a WCU will lookup existing PINs for HIA, HIB, and Diagnostic firewall disable. If available the PINs will be applied to their corresponding fields. If not all PINs are available there will be a pop-up specifying which PINs are unavailable and for which reason: either missing entirely or there exists a PIN for the ECU but for the wrong service area.<br />
<br />
For resource groups '''Check PINs''' will not apply any found PINs, instead if there are any resources with missing PINs it will specify, like for individual WCUs, which PINs are missing and for which WCUs.<br />
<br />
To apply PINs for resource groups see [[I/O configurations#Apply uploaded PINs|apply uploaded PINs]] below.<br />
== Apply uploaded PINs ==<br />
Option for resource groups to apply uploaded PINs for HIA, HIB, and Diagnostic firewall disable. Resets back to unchecked after saving the configuration. Visible for WCUs with version 2.89.0 or later.<br />
<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). As of 2.94.0 the PINs may also be fetched from PIE via ''Administration''->''Resource group''s'','' read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=I/O_configurations&diff=3969I/O configurations2025-06-13T09:15:50Z<p>Robin.karhu: /* Apply uploaded PINs */</p>
<hr />
<div><div class="keywords"> io, io configurations, io config, io configs </div><br />
<includeonly>= I/O configurations =</includeonly><br />
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".<br />
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]<br />
<br />
==Edit CAN channels==<br />
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]<br />
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.<br />
<br />
===Channel===<br />
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.<br />
<br />
===Speed (kB)===<br />
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.<br />
<br />
=== FD Speed (kB) ===<br />
[[File:Wcu-configuration-can-fd.png|alt=CAN FD setting for the HMX platform|thumb|CAN FD setting for the HMX platform]]<br />
If the platform is HMX and the WCU version is 2.91.0 or later, a column will appear for the CAN channel. <br />
<br />
===Name===<br />
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.<br />
<br />
===Comment===<br />
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.<br />
<br />
===Add WMU(s)===<br />
If your Portal has [[WMU | WMU's]] enabled the "Add WMU" button will show in the CAN section. You can then add/remove WMU's and configure their CAN channels in the same way as the WCU's CAN channels are configured. For each WMU that is added, a corresponding tab is added under the [[The_Portal_Administrator_View#WMU's_Power_Management | Power Management tab]] for configuring the WMU's power behaviour.<br />
<br />
=== Add CAN channels ===<br />
If your Portal has Vehicle Communication Forwarder enabled, the "Add CAN channels" button will show in the CAN section. If both WMUs and Vehicle Communication Forwarder are enabled in your Portal, only "Add CAN channels" will show up. After having added a Vehicle Communication Forwarder with at least one CAN channel, pressing the button again will add more CAN channels to the Vehicle Communication Forwarder. When removing CAN channels, it is possible to either remove the entire Vehicle Communication Forwarder, or individual CAN channels from it.<br />
<br />
==Edit Ethernet Channels==<br />
[[File:NewEthernetChannel.png|thumb|Edit Ethernet Channels]]<br />
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains eight columns and the individual meaning is as follows.<br />
<br />
===Channel===<br />
This column indicates which interface or interfaces that exists.<br />
<br />
===Addressing mode===<br />
In this column the Addressing mode is configured. The choices are "DHCP client", "AutoIP" and "Static".<br />
<br />
===IP address===<br />
Here you set the static IP address if you have selected "Static" as the Addressing mode.<br />
<br />
===Netmask===<br />
Here you set the netmask if you have selected "Static" as the Addressing mode.<br />
<br />
===Default route===<br />
Here you set the default route if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. The default route is the route that takes effect when no other route is available for an IP destination address.<br />
<br />
===Name Server (DNS)===<br />
Here you set the Name Server if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. Here you set the name of the DNS protocol.<br />
<br />
===Name===<br />
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.<br />
<br />
===Comment===<br />
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.<br />
<br />
==The Miscellaneous Section==<br />
[[File:Screenshot from 2024-09-16 09-49-47.png|thumb|Miscellaneous]]<br />
This section is available for WCUs with version 2.49 or later.<br />
===Set digital out 3 on boot=== <br />
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).<br />
<br />
===Diagnostic tester priority===<br />
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".<br />
<br />
=== Allow ethernet activation on WCU ===<br />
For WCUs of version 2.90.4 or later it is possible to choose whether or not to allow the WCU to use ethernet activation. Not allowing this might disturb some of the WCUs features.<br />
<br />
===Set 5V out on boot===<br />
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.<br />
<br />
===Activate buzzer on detected digital input change===<br />
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.<br />
<br />
=== Diagnostic firewall disable and PIN ===<br />
Option to disable diagnostic firewall. Requires PIN. Visible for WCUs with version 2.89.0 or later.<br />
<br />
==Manage templates==<br />
[[File:Io config2.png|thumb|frame|Selecting Template]]<br />
Admins can save configs as templates (see [[#Manage templates (for admins) | Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.<br />
Clicking "Apply" will apply the selected template. You can always change settings or add more info, the template could be anything you need or just act as a starting point.<br />
<br />
If WMUs are enabled in the portal, a template will save the CANs from each WMU and when a template is selected the WMU CANs are applied 1:1 to each existing WMU in the configuration. <br />
If there are no WMUs in the configuration the template's WMU CANs will not be applied, only the WCU's CANs.<br />
<br />
==Manage templates (for admins)==<br />
[[File:Io config3.png|thumb|frame|Manage Templates (admin view)]]<br />
[[File:Io config4.png|thumb|frame|Manage Templates (with WMUs enabled)]]<br />
If you are an admin you have an extra button "Save current config as template" in the Manage configuration templates window. Clicking it to save the current configuration as a template will prompt you for a name. If the name already exists (case insensitive) a confirmation dialog will popup before overwriting.<br />
<br />
Additionally, as admin you will be able to remove existing templates, which is done by clicking the red "Remove record" icon to the right of the template name. A confirmation dialog will popup to prevent deletion by mistake.<br />
<br />
==Show Vehicle Profile==<br />
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]<br />
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.<br />
<br />
== Check PINs ==<br />
Requires version 2.89.0 or later. Pressing '''Check PINs''' for a WCU will lookup existing PINs for HIA, HIB, and Diagnostic firewall disable. If available the PINs will be applied to their corresponding fields. If not all PINs are available there will be a pop-up specifying which PINs are unavailable and for which reason: either missing entirely or there exists a PIN for the ECU but for the wrong service area.<br />
<br />
For resource groups '''Check PINs''' will not apply any found PINs, instead if there are any resources with missing PINs it will specify, like for individual WCUs, which PINs are missing and for which WCUs.<br />
<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). As of 2.94.0 the PINs may also be fetched from PIE via ''Administration''->''Resource group''s'','' read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]].<br />
== Apply uploaded PINs ==<br />
Option for resource groups to apply uploaded PINs for HIA, HIB, and Diagnostic firewall disable. Resets back to unchecked after saving the configuration. Visible for WCUs with version 2.89.0 or later.<br />
<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). As of 2.94.0 the PINs may also be fetched from PIE via ''Administration''->''Resource group''s'','' read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=I/O_configurations&diff=3968I/O configurations2025-06-13T09:15:26Z<p>Robin.karhu: /* Check PINs */</p>
<hr />
<div><div class="keywords"> io, io configurations, io config, io configs </div><br />
<includeonly>= I/O configurations =</includeonly><br />
<noinclude>The following applies to version >= 2.41 of the portal:</noinclude>For WCUs with software version >= 2.41 the "Edit Configuration" window has a new tab named "IO". In this tab, it is possible to edit the settings of the CAN and Ethernet channels of a WCU. It is also possible to apply a pre defined template which is created and managed by an admin. The "Edit Configuration" window is reached by going to the Vehicles tab, select a WCU and press the button "Edit Configuration".<br />
[[File:Edit configuration IO.png|thumb|Edit Configuration: IO.]]<br />
<br />
==Edit CAN channels==<br />
[[File:WCU conf io can channels.png|thumb|Edit CAN Channels]]<br />
The number of available CAN channels depends on the platform type of the WCU which is configured. The group of CAN channels consists of four columns named Channel, Speed, Name and Comment. Each column is described separately below.<br />
<br />
===Channel===<br />
This column is a checkbox and if you enable CAN X, this means that X is available for mappings when creating a new task and uploading this task to his WCU. Read more about [[Mappings]]. In the same way, disabling CAN X means that X is not available for mappings. If a CAN channel for some reason is not connected to the WCU, then it could be good choice to disabling it here.<br />
<br />
===Speed (kB)===<br />
The speed column shows the baud rate of each CAN channel. This value was previously added to the WCU configuration when the WCU was connected to a CAR but from now it has to be set manually in this tab.<br />
<br />
=== FD Speed (kB) ===<br />
[[File:Wcu-configuration-can-fd.png|alt=CAN FD setting for the HMX platform|thumb|CAN FD setting for the HMX platform]]<br />
If the platform is HMX and the WCU version is 2.91.0 or later, a column will appear for the CAN channel. <br />
<br />
===Name===<br />
In this column it is possible to set a nickname for the channel. This name is used when a Signalreader task or assignment is automapped (see [[Mappings]]) so choose your names carefully. The default value is CAN 1,2..6.<br />
<br />
===Comment===<br />
The last column is used to add some comments to each channel. This is typically some describing text, e.g. the reason why a channel is disabled.<br />
<br />
===Add WMU(s)===<br />
If your Portal has [[WMU | WMU's]] enabled the "Add WMU" button will show in the CAN section. You can then add/remove WMU's and configure their CAN channels in the same way as the WCU's CAN channels are configured. For each WMU that is added, a corresponding tab is added under the [[The_Portal_Administrator_View#WMU's_Power_Management | Power Management tab]] for configuring the WMU's power behaviour.<br />
<br />
=== Add CAN channels ===<br />
If your Portal has Vehicle Communication Forwarder enabled, the "Add CAN channels" button will show in the CAN section. If both WMUs and Vehicle Communication Forwarder are enabled in your Portal, only "Add CAN channels" will show up. After having added a Vehicle Communication Forwarder with at least one CAN channel, pressing the button again will add more CAN channels to the Vehicle Communication Forwarder. When removing CAN channels, it is possible to either remove the entire Vehicle Communication Forwarder, or individual CAN channels from it.<br />
<br />
==Edit Ethernet Channels==<br />
[[File:NewEthernetChannel.png|thumb|Edit Ethernet Channels]]<br />
Like for CAN channels, the number of available Ethernet channels depends on the platform type of the WCU which is configured. The group of Ethernet channels contains eight columns and the individual meaning is as follows.<br />
<br />
===Channel===<br />
This column indicates which interface or interfaces that exists.<br />
<br />
===Addressing mode===<br />
In this column the Addressing mode is configured. The choices are "DHCP client", "AutoIP" and "Static".<br />
<br />
===IP address===<br />
Here you set the static IP address if you have selected "Static" as the Addressing mode.<br />
<br />
===Netmask===<br />
Here you set the netmask if you have selected "Static" as the Addressing mode.<br />
<br />
===Default route===<br />
Here you set the default route if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. The default route is the route that takes effect when no other route is available for an IP destination address.<br />
<br />
===Name Server (DNS)===<br />
Here you set the Name Server if you have selected "Static" as the Addressing mode. This field only shows if the WCU software version is 2.85.0 or later. Here you set the name of the DNS protocol.<br />
<br />
===Name===<br />
In this column you can set a nickname for this channel. This setting has no effect on the WCU side.<br />
<br />
===Comment===<br />
In the last column you can set a comment for this channel. Like for the name, this setting has no effect on the WCU side.<br />
<br />
==The Miscellaneous Section==<br />
[[File:Screenshot from 2024-09-16 09-49-47.png|thumb|Miscellaneous]]<br />
This section is available for WCUs with version 2.49 or later.<br />
===Set digital out 3 on boot=== <br />
Digital out 3 is one of the output pins in the dsub contact on WCUs of model MX4. This setting activates that pin on start-up of the WCU. The purpose of this is to trigger an external measurement equipment (e.g. [[Creating_a_Task#M-Log|M-Log]] or [[Creating_a_Task#Arcos|Arcos]]).<br />
<br />
===Diagnostic tester priority===<br />
For WCUs of version later than or equal to 2.60 it is possible to choose to configure the diagnostic tester priority. If enabled, a value between 1-12 can be selected. The described options are depicted in Figure "Miscellaneous".<br />
<br />
=== Allow ethernet activation on WCU ===<br />
For WCUs of version 2.90.4 or later it is possible to choose whether or not to allow the WCU to use ethernet activation. Not allowing this might disturb some of the WCUs features.<br />
<br />
===Set 5V out on boot===<br />
Option to set one of the output pins on the WCU to supply electricity at 5V to external equipment when the WCU is starting up. The option is visible for WCUs of model MX4 (except submodel V61) and with version 2.76.0 or later.<br />
<br />
===Activate buzzer on detected digital input change===<br />
Option to enable that the WCU makes a buzzing sound when a trigger-button (or other digital input) is activated on the WCU. It is possible on all MX4 models. The option is visible for WCUs with version 2.76.0 or later.<br />
<br />
=== Diagnostic firewall disable and PIN ===<br />
Option to disable diagnostic firewall. Requires PIN. Visible for WCUs with version 2.89.0 or later.<br />
<br />
==Manage templates==<br />
[[File:Io config2.png|thumb|frame|Selecting Template]]<br />
Admins can save configs as templates (see [[#Manage templates (for admins) | Manage templates (for admins)]]) and normal users can use these templates to fill all columns with the data stored in the template.<br />
Clicking "Apply" will apply the selected template. You can always change settings or add more info, the template could be anything you need or just act as a starting point.<br />
<br />
If WMUs are enabled in the portal, a template will save the CANs from each WMU and when a template is selected the WMU CANs are applied 1:1 to each existing WMU in the configuration. <br />
If there are no WMUs in the configuration the template's WMU CANs will not be applied, only the WCU's CANs.<br />
<br />
==Manage templates (for admins)==<br />
[[File:Io config3.png|thumb|frame|Manage Templates (admin view)]]<br />
[[File:Io config4.png|thumb|frame|Manage Templates (with WMUs enabled)]]<br />
If you are an admin you have an extra button "Save current config as template" in the Manage configuration templates window. Clicking it to save the current configuration as a template will prompt you for a name. If the name already exists (case insensitive) a confirmation dialog will popup before overwriting.<br />
<br />
Additionally, as admin you will be able to remove existing templates, which is done by clicking the red "Remove record" icon to the right of the template name. A confirmation dialog will popup to prevent deletion by mistake.<br />
<br />
==Show Vehicle Profile==<br />
[[File:WCU conf io car interf.png|thumb|Vehicle Profile]]<br />
The button "Show vehicle profile" can be used to show, and hide, a panel showing the CAN and ethernet information for the connected car, see Figure "Vehicle Profile". This option is disabled if no car is connected.<br />
<br />
== Check PINs ==<br />
Requires version 2.89.0 or later. Pressing '''Check PINs''' for a WCU will lookup existing PINs for HIA, HIB, and Diagnostic firewall disable. If available the PINs will be applied to their corresponding fields. If not all PINs are available there will be a pop-up specifying which PINs are unavailable and for which reason: either missing entirely or there exists a PIN for the ECU but for the wrong service area.<br />
<br />
For resource groups '''Check PINs''' will not apply any found PINs, instead if there are any resources with missing PINs it will specify, like for individual WCUs, which PINs are missing and for which WCUs.<br />
<br />
PINs must first have been be uploaded via either the '''Upload Vehicle PINs''' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting '''Upload Vehicle PINs''' (for a single vehicle). As of 2.94.0 the PINs may also be fetched from PIE via ''Administration''->''Resource group''s'','' read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]].<br />
== Apply uploaded PINs ==<br />
Option for resource groups to apply uploaded PINs for HIA, HIB, and Diagnostic firewall disable. Resets back to unchecked after saving the configuration. Visible for WCUs with version 2.89.0 or later.<br />
<br />
PINs must first have been be uploaded via either the 'Upload Vehicle PINs' button in the vehicles tab (for multiple vehicles), or by right-clicking a WCU and selecting 'Upload Vehicle PINs' (for a single vehicle). As of 2.94.0 the PINs may also be fetched from PIE via ''Administration''->''Resource group''s'','' read more about fetching PINs from PIE [[The Portal Administrator View#The Resource Groups Tab|here]].</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicle_Communication_Forwarder&diff=3967Vehicle Communication Forwarder2025-06-13T09:14:48Z<p>Robin.karhu: </p>
<hr />
<div>A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.<br />
<br />
Requires WCU version 2.89.0 or higher.<br />
<br />
For WCU versions 2.91.0 or higher it is also possible to configure LIN channels on the VCF.<br />
<br />
To read more about adding a VCF, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.<br />
<br />
The fields HIA PIN and HIB PIN need to be set for the VCF to function correctly. In the miscellaneous section of the IO tab there are settings for diagnostic firewall disable which may also need to be set for the VCF to function correctly. In addition to setting these PINs manually it is possible to upload PINs from file for either [[Vehicles#Right click context menu|individual]] or for [[Vehicles#Upload Vehicle pins|multiple]] vehicles. As of 2.94.0 it will also be possible to [[The Portal Administrator View#The Resource Groups Tab|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they can be applied via the I/O configuration of either the resource group or an individual WCU, to read more about applying PINs see [[I/O configurations#Apply uploaded PINs|here]] and about checking PINs [[I/O configurations#Check PINs|here]].<br />
[[File:Vehicle Communications Forwarder CAN channels.png|thumb|CAN channel configuration|769x769px]]<br />
[[File:VCF LIN - 2.91.0.png|thumb|768x768px|CAN and LIN channel configurations]]</div>Robin.karhuhttps://wiki.alkit.se/wice297/index.php?title=Vehicle_Communication_Forwarder&diff=3966Vehicle Communication Forwarder2025-06-13T09:12:52Z<p>Robin.karhu: </p>
<hr />
<div>A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.<br />
<br />
Requires WCU version 2.89.0 or higher.<br />
<br />
For WCU versions 2.91.0 or higher it is also possible to configure LIN channels on the VCF.<br />
<br />
To read more about adding a VCF, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.<br />
<br />
The fields HIA PIN and HIB PIN need to be set for the VCF to function correctly. Additionally, in the miscellaneous section of the IO tab there are settings for diagnostic firewall disable which may also need to be set for the VCF to function correctly. In addition to setting these PINs manually it is possible to upload PINs from file for either [[Vehicles#Right click context menu|individual]] or for [[Vehicles#Upload Vehicle pins|multiple]] vehicles. As of 2.94.0 it will also be possible to [[The Portal Administrator View#The Resource Groups Tab|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they can be applied via the I/O configuration of either the resource group or an individual WCU, to read more about applying PINs see [[I/O configurations#Apply uploaded PINs|here]] and about checking PINs [[I/O configurations#Check PINs|here]].<br />
[[File:Vehicle Communications Forwarder CAN channels.png|thumb|CAN channel configuration|769x769px]]<br />
[[File:VCF LIN - 2.91.0.png|thumb|768x768px|CAN and LIN channel configurations]]</div>Robin.karhu