Difference between revisions of "New features in v2.72"
| (11 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
== DLT task supports several daemons == | == DLT task supports several daemons == | ||
[[File:New-task-dlt-2-72.png|thumb|The DLT new task dialog]] | [[File:New-task-dlt-2-72.png|thumb|The DLT new task dialog|200x200px]] | ||
The [[Creating a Task#Diagnostic Log and Trace (DLT)|Diagnostic Log and Trace (DLT)]] task can now fetch logs from several daemons. | The [[Creating a Task#Diagnostic Log and Trace (DLT)|Diagnostic Log and Trace (DLT)]] task can now fetch logs from several daemons. | ||
| Line 9: | Line 9: | ||
== File fetcher: A new | == File fetcher: A new module to fetch files from other units in vehicle (Not in all versions of the Portal) == | ||
[[File:New-task-file-fetcher-2x72.png|thumb|New task dialog of the File fetcher task.]] | [[File:New-task-file-fetcher-2x72.png|thumb|New task dialog of the File fetcher task.|200x200px]] | ||
[[Creating a Task#File fetcher|The File fetcher task]] will make the WCU fetch files from another unit in the vehicle and make them available for downloading in the Portal. | [[Creating a Task#File fetcher|The File fetcher task]] will make the WCU fetch files from another unit in the vehicle and make them available for downloading in the Portal. | ||
| Line 25: | Line 25: | ||
== VIN reader supports method "DoIP" == | == VIN reader supports method "DoIP" == | ||
It is now possible to choose DoIP as a VIN reader method in the [[The Portal Administrator View#Configure the Vinreader Module|VIN reader module]]. | It is now possible to choose DoIP as a VIN reader method in the [[The Portal Administrator View#Configure the Vinreader Module|VIN reader module]]. | ||
== WCU History: new searchable columns "WCU Version" and "WCU Firmware Version" == | == WCU History: new searchable columns "WCU Version" and "WCU Firmware Version" == | ||
In [[Vehicles|the Vehicles tab]], when right-clicking a WCU and choosing "Show WCU history", a dialog window with the changes | In [[Vehicles|the Vehicles tab]], when right-clicking a WCU and choosing "Show WCU history", a dialog window with the changes made to the WCU shows up. | ||
This release adds two new ''searchable'' columns to this dialog window: | This release adds two new ''searchable'' columns to this dialog window: | ||
| Line 34: | Line 35: | ||
* '''WCU Firmware version''' - shows when a new firmware version has been applied to the WCU. | * '''WCU Firmware version''' - shows when a new firmware version has been applied to the WCU. | ||
The columns are searched in with | The columns are searched using [[Tasks Tab#Search columns with regular expressions|regular expressions]]. | ||
== Support for UDS (2C/2A) and XCP over CAN for A2L-based signals in the Signal Reader Assignment Editor == | |||
From version 2.72, Signal Reader supports UDS (service 2C/2A) and XCP/CAN communication for A2L-based signals. In the Signal Reader Assignment Editor the selection of whether to use UDS or XCP/CAN (or the previously available CCP/CAN, XCP/UDP or XCP/TCP) for A2L Signals is done in the Modules tab. For more information about this, see [[Signal Reader Assignment Editor]]. | |||
== Module settings for Signal Reader now has support for selecting DoIP as default diagnostic channel == | |||
In the module settings for Signal Reader you can now select DoIP as default channel. This affects diagnostics based signals and DRECs. When DoIP is selected as the default interface it is also possible to select static IP or the IP that the vehicle announces. | |||
== Signal Reader Assignment Editor shows IP address and port from A2L-file == | |||
In the assignment editor for Signal Reader, for communication interfaces over Ethernet (XCP/UDP and XCP/TCP), the IP address and port that is specified in the A2L file is displayed. It is also possible to change the address and port for the specific assignment in the same window. | |||
== Edit test request name (Not in all versions of the Portal) == | |||
A new button has been added to the Edit Vehicle-dialog which is reached by going to [[Vehicles|the Vehicles tab]], choosing a vehicle and pressing the "Edit Vehicle"-button. | |||
[[File:Edit-vechicle-with-edit-test-request-name-btn-ver-2x72.png|thumb|The new button showing in the "Edit vechicle"-dialog. Not all versions of the Portal contain this button.]] | |||
The new button is called "Edit test request name". It opens a window containing information about test-labels and associated names. These associated names, also known as "Test request names", can be edited or added for each test label value (TCPxRef value). | |||
Latest revision as of 08:39, 7 February 2022
DLT task supports several daemons
The Diagnostic Log and Trace (DLT) task can now fetch logs from several daemons.
Previously the task could only have one daemon. Then the address and port number of the daemon were specified in the DLT Module, while the filters to be applied to the logs were specified while creating the task itself. This is still the case for WCUs that have a software version earlier than 2.72.0.
From this release the addresses and port numbers for each daemon as well as the filters are specified while creating the task, given that the software version of the WCUs are 2.72.0. The only thing that hereby is specified in the DLT Module is the debug level.
File fetcher: A new module to fetch files from other units in vehicle (Not in all versions of the Portal)
The File fetcher task will make the WCU fetch files from another unit in the vehicle and make them available for downloading in the Portal.
The following needs to be specified when creating such a task:
- File path - The path to a file or file-containing directory on the unit's file system. This specifies which files that will be fetched.
- Username - To log in to the unit.
- Password - To log in to unit.
- IP address - To find the unit.
- Port - To find the unit.
The File fetcher module only contains debug level to steer the log output of the WCU when it is handling the task.
VIN reader supports method "DoIP"
It is now possible to choose DoIP as a VIN reader method in the VIN reader module.
WCU History: new searchable columns "WCU Version" and "WCU Firmware Version"
In the Vehicles tab, when right-clicking a WCU and choosing "Show WCU history", a dialog window with the changes made to the WCU shows up.
This release adds two new searchable columns to this dialog window:
- WCU Version - Shows when a new version has been applied to the WCU.
- WCU Firmware version - shows when a new firmware version has been applied to the WCU.
The columns are searched using regular expressions.
Support for UDS (2C/2A) and XCP over CAN for A2L-based signals in the Signal Reader Assignment Editor
From version 2.72, Signal Reader supports UDS (service 2C/2A) and XCP/CAN communication for A2L-based signals. In the Signal Reader Assignment Editor the selection of whether to use UDS or XCP/CAN (or the previously available CCP/CAN, XCP/UDP or XCP/TCP) for A2L Signals is done in the Modules tab. For more information about this, see Signal Reader Assignment Editor.
Module settings for Signal Reader now has support for selecting DoIP as default diagnostic channel
In the module settings for Signal Reader you can now select DoIP as default channel. This affects diagnostics based signals and DRECs. When DoIP is selected as the default interface it is also possible to select static IP or the IP that the vehicle announces.
Signal Reader Assignment Editor shows IP address and port from A2L-file
In the assignment editor for Signal Reader, for communication interfaces over Ethernet (XCP/UDP and XCP/TCP), the IP address and port that is specified in the A2L file is displayed. It is also possible to change the address and port for the specific assignment in the same window.
Edit test request name (Not in all versions of the Portal)
A new button has been added to the Edit Vehicle-dialog which is reached by going to the Vehicles tab, choosing a vehicle and pressing the "Edit Vehicle"-button.
The new button is called "Edit test request name". It opens a window containing information about test-labels and associated names. These associated names, also known as "Test request names", can be edited or added for each test label value (TCPxRef value).