Creating a Task - Revision history

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.

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

2023-12-14T08:38:42Z

Announce result file availability

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

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

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

Jonas: /* SWDL */

2023-06-28T13:41:05Z

SWDL

← Older revision		Revision as of 13:41, 28 June 2023
Line 211:		Line 211:
	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.		By checking the box '''Run SoH after completion''' it is possible to let the SWDL task run the WCUs SoH task after the SWDL task is completed.

	If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "'''Use Vehicle Pin mappings'''". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes here.		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]].

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

Jonas: /* SWDL */

2023-06-28T12:57:01Z

SWDL

← Older revision		Revision as of 12:57, 28 June 2023
Line 200:		Line 200:

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

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

	SWDL tasks can optionally include one '''signature file''' (containing checksums). The file is assumed to be ~~a .~~xml-file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)		SWDL tasks can optionally include one '''signature file''' (containing checksums). The file is assumed to be an xml file. (Available from WCU version 2.66) If either of the optional files is selected, a field will appear to the right of the chosen file. This field will contain the name of the chosen file. (Available from WCU version 2.70)

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

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

			If you would like to use any individual ECU pin codes for a vehicle, make sure to check the box "'''Use Vehicle Pin mappings'''". If a pin code for the ECU targeted by a vbf file, the pin code for the vehicle will be used. If no such pin code is found, the one entered in the right hand side table is used. Read more on how to prepare a vehicle with pin codes here.

	SWDL tasks can optionally contain a '''Trigger Expression''' which must be fulfilled within a specified time limit ("Wait time") for ECU re-programming to be allowed. The trigger expression follows the same syntax as Signal Reader trigger expressions (or [[Server 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.		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.

Jonathan.olsson: /* CAN-recorder */

2023-06-28T12:26:17Z

CAN-recorder

← Older revision		Revision as of 12:26, 28 June 2023
Line 46:		Line 46:
	Canrecorder is a measurement module that allows CAN frames to be captured and logged.		Canrecorder is a measurement module that allows CAN frames to be captured and logged.

	1. In the grid, select which bus (or buses) to record from. By clicking below active column or select a row and click on ~~toggle~~ button.		1. In the grid, select which bus (or buses) to record from. By clicking below active column or select a row and click on “Toggle” button.

	2. ~~Specify which~~ CAN ~~frames you want~~ to ~~record by entering their CAN IDs in the CAN~~ frame ~~ID column in the grid, on the same row as the bus you have selected,~~ or by ~~entering the IDs in the text box labeled “Set filters on selected CAN buses”. If you use the latter option~~, ~~the filters will be set on all of the buses you have selected~~. ~~To enter~~ a ~~filter on a specific bus use the method of entering the filter on the same row as the selected bus, on the grid~~. ~~This~~ can ~~only~~ be ~~done if the CAN frame passthrough filter is turned on~~. ~~Turning off the CAN frame passthrough~~ filter ~~option will disable the CAN frame ID column in the grid. Press the “Clear All” button to remove all the entered filters from all buses.~~		2. To apply filters on specific CAN buses, select a row and click on “Edit filter”. There it is possible to select one specific frame or several by separating them by “,”. It is also possible to select a range between frames by using “-”. The value can either be decimal or hexadecimal. A example of a filter: “1, 0x12-0xFF”

	3. ~~Turning on or off a CAN frame pass-through filter. If you choose to have~~ the ~~filter on you must specify which CAN bus or CAN buses you wish to record.~~		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.

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

	===Scheduling===		===Scheduling===