Creating a Task - Revision history

Robin.karhu: /* DLT UDS Mode */

2026-02-19T17:50:34Z

DLT UDS Mode

← Older revision		Revision as of 17:50, 19 February 2026
Line 79:		Line 79:

	=== DLT UDS Mode ===		=== DLT UDS Mode ===
	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.		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.
	[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]		[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]
	~~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~~]].		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]].

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

	== ETAS ==		== ETAS ==

Robin.karhu: /* Software version validation (Available from version 2.74.0) */

2025-11-06T15:08:36Z

Software version validation (Available from version 2.74.0)

← Older revision		Revision as of 15:08, 6 November 2025
Line 139:		Line 139:
	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.		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.

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

			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.

	== MQTT ==		== MQTT ==

Patrik.Nyborg: Soh image including Build ID

2025-11-06T12:22:06Z

Soh image including Build ID

← Older revision		Revision as of 12:22, 6 November 2025
Line 189:		Line 189:

	== SoH ==		== SoH ==
	[[File:~~Screenshot from 2021-04-01 09-43-34~~.png\|thumb\|799x799px\|SoH]]		[[File:SoH.png\|thumb\|799x799px\|SoH]]
	A State of Health (SoH) task collects specific status information from vehicles. You select which information you want the task to collect by filling in one or more of the checkboxes shown in Figure "SoH". The number of checkboxes shown can vary depending on the WICE installation. In order for SoH data to be correctly interpreted, relevant description files (e.g. SDDB) for the vehicles executing the SoH task may have to been available. To add such a description file for a vehicle, see [[The_Portal_Administrator_View#The_Edit_Car_Dialog\|The Edit Car Dialog]].The six different options are:		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:
	*Mileage		*Mileage
Line 197:		Line 197:
	*Read OBD-II PIDs		*Read OBD-II PIDs
	*App Diagnotstic Db Part Num		*App Diagnotstic Db Part Num
			*Build ID
	*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939\|j1939 protocol]]		*DM1, Diagnostic Message using the [[wikipedia:SAE_J1939\|j1939 protocol]]
	*Odometer, reading the odometer using the [[wikipedia:SAE_J1939\|j1939 protocol]] (available from WCU version 2.63)		*Odometer, reading the odometer using the [[wikipedia:SAE_J1939\|j1939 protocol]] (available from WCU version 2.63)

Alkitjohan: /* Diagnostic Log and Trace (DLT) */

2025-11-03T14:15:26Z

Diagnostic Log and Trace (DLT)

← Older revision		Revision as of 14:15, 3 November 2025
Line 63:		Line 63:

	== Diagnostic Log and Trace (DLT) ==		== Diagnostic Log and Trace (DLT) ==
	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".		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".
			[[File:DLT multi task and vehicle announcement.png\|thumb\|DLT multi task and get DLT Daemon address from vehicle announcement]]
			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.

	=== DLT Daemon Mode ===		=== DLT Daemon Mode ===
	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].		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].
	~~[[File:New-dlt-daemon.png\|thumb\|The DLT new task dialog for the daemon mode.]]~~
	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.		Basically the WCU is connecting to one or more DLT Daemons and unique filters can be applied to each daemon, filtering out specific log messages.

	So when creating a DLT task ~~on WCUs with software version 2.72.0 or later~~ the number of daemons can be specified and for each daemon the following needs to be specified:		So when creating a DLT task the number of daemons can be specified and for each daemon the following needs to be specified:

	# Daemon address - the IP-address in order for the WCUs DLT client to find the daemon.		# Daemon 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.
	# Daemon port - which port on the address the daemon is at.		# Daemon port - which port on the address the daemon is at.
	# Filter configurations - filter expressions to be applied on the log messages. If left empty no filter is applied. For an explanation on how to write filter expressions, see [https://github.com/GENIVI/dlt-daemon#learn-more here].		# 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].

	~~==== Older WCUs ====~~
	For WCUs with software version earlier than 2.72.0 only one daemon is supported and only filters can be configured when creating a DLT task. To specify the daemon address and port go to the [[DLT Module]] instead.

	=== DLT UDS Mode ===		=== DLT UDS Mode ===

Robin.karhu: /* DLT UDS Mode */

2025-08-28T11:36:09Z

DLT UDS Mode

← Older revision		Revision as of 11:36, 28 August 2025
Line 83:		Line 83:
	[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]		[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]
	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]].		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]].

			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.

	== ETAS ==		== ETAS ==

Jonas: /* DLT UDS Mode */

2024-12-13T13:16:55Z

DLT UDS Mode

← Older revision		Revision as of 13:16, 13 December 2024
Line 82:		Line 82:
	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.		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.
	[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]		[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]
	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. How to supply the system with ~~suck~~ PIN codes ~~can be done over~~ [[Vehicles#Upload Vehicle pins\|here]].		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]].

	== ETAS ==		== ETAS ==

Jonas: /* DLT UDS Mode */

2024-12-13T13:15:25Z

DLT UDS Mode

← Older revision		Revision as of 13:15, 13 December 2024
Line 82:		Line 82:
	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.		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.
	[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]		[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]
	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. How to supply the system with suck PIN codes can be done over here ~~(link to Robins stuff)~~.		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. How to supply the system with suck PIN codes can be done over [[Vehicles#Upload Vehicle pins\|here]].

	== ETAS ==		== ETAS ==

Jonas: /* Diagnostic Log and Trace (DLT) */

2024-12-13T09:43:41Z

Diagnostic Log and Trace (DLT)

← Older revision		Revision as of 09:43, 13 December 2024
Line 63:		Line 63:

	== Diagnostic Log and Trace (DLT) ==		== Diagnostic Log and Trace (DLT) ==
	DLT itself provides a log and trace interface, based on the ~~standardised~~ protocol specified in the AUTOSAR standard 4.0 DLT. A DLT task in the WICE Portal makes it possible to collect such logs in a vehicle where this functionality is available and transfer the data to the WICE portal where logs can be downloaded for further analysis. For a more in-depth description, you can go [https://github.com/GENIVI/dlt-daemon here].		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".
	[[File:New~~-task~~-dlt-~~2-72~~.png\|thumb\|The DLT new task dialog.]]
			=== DLT Daemon Mode ===
			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].
			[[File:New-dlt-daemon.png\|thumb\|The DLT new task dialog for the daemon mode.]]
	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.		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.

Line 75:		Line 78:
	==== Older WCUs ====		==== Older WCUs ====
	For WCUs with software version earlier than 2.72.0 only one daemon is supported and only filters can be configured when creating a DLT task. To specify the daemon address and port go to the [[DLT Module]] instead.		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.

			=== DLT UDS Mode ===
			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.
			[[File:Dlt-uds-task.png\|thumb\|DLT UDS service 38 task]]
			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. How to supply the system with suck PIN codes can be done over here (link to Robins stuff).

	== ETAS ==		== ETAS ==

Jonas: /* Announce result file availability */

2023-12-14T15:01:35Z

Announce result file availability

← Older revision		Revision as of 15:01, 14 December 2023
Line 241:		Line 241:

	==== Announce result file availability ====		==== Announce result file availability ====
	[[File:Resultfilepanel.png\|thumb\|~~AnnouncedOn~~ column]]		[[File:Resultfilepanel.png\|thumb\|Announced On column]]
	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 '~~AnnouncedOn~~' column that keeps track of when the result file was announced.		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.

	==== Retention time ====		==== Retention time ====

Henrik.Moller: /* Announce result file availability */

2023-12-14T08:47:31Z

Announce result file availability

← Older revision		Revision as of 08:47, 14 December 2023
Line 241:		Line 241:

	==== Announce result file availability ====		==== Announce result file availability ====
			[[File:Resultfilepanel.png\|thumb\|AnnouncedOn column]]
	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 'AnnouncedOn' column that keeps track of when the result file was announced.		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 'AnnouncedOn' column that keeps track of when the result file was announced.