Difference between revisions of "DLT Module"
Jump to navigation
Jump to search
(described new module from 2.72) |
|||
| Line 5: | Line 5: | ||
=== WCUs with version 2.72.0 or later === | === WCUs with version 2.72.0 or later === | ||
From this version the WCU can connect to multiple daemons. Therefore the daemon addresses and ports are specified when creating a [[Creating a Task#Diagnostic Log and Trace (DLT)|Diagnostic Log and Trace (DLT) task]] instead. The only thing specified in the module is the debug level - the level of logging from the WCU regarding its handling of this task and not information from the task itself. | From this version the WCU can connect to multiple daemons. Therefore the daemon addresses and ports are specified when creating a [[Creating a Task#Diagnostic Log and Trace (DLT)|Diagnostic Log and Trace (DLT) task]] instead. The only thing specified in the module is the [[debug level]] - the level of logging from the WCU regarding its handling of this task and not information from the task itself. | ||
Latest revision as of 15:20, 2 February 2022
WCUs with version earlier than 2.72.0
The settings for the DLT module consists of two parts. First, you must enter an address in order for the WCUs DLT client to be able to connect to the DLT daemon running in the vehicle. Secondly, the port of the daemon must also be set. A default port is chosen, but it can be changed if desired. In the illustration on the right you can see the settings available.
WCUs with version 2.72.0 or later
From this version the WCU can connect to multiple daemons. Therefore the daemon addresses and ports are specified when creating a Diagnostic Log and Trace (DLT) task instead. The only thing specified in the module is the debug level - the level of logging from the WCU regarding its handling of this task and not information from the task itself.