New features in v2.97

Add all signals and multiple signal sources for signal reader in the assignment editor.

It is now possible to select multiple signal sources for a Signal Reader Recorder, instead of being limited to a single source.

An “Add All” button has been introduced, allowing users to add either all available signals or only the filtered selection.

A corresponding “Remove All” button is available in the Recorder, with the option to remove either all signals or only the filtered selection.

Support for WCU hardened mode.

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 “hardened.”

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.

Support for automatically generating passwords

Admins can now automatically generate a new password for a user directly from the User panel’s Change Password dialog. Learn more here.

Additional settings for ethernet interfaces on HMX for automotive Ethernet

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

Configurable default time interval for alarms in portal

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

Improvements to Creating/View Mapping on Signal Reader Task

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.

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, click here.

Improved timestamping in Signal Reader

The timestamping in MDF files generated by Signal Reader is improved by using the timestamps supplied by the CAN controller.

Changes to DLT tasks

Edit DLT tasks

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.

Enable scheduling for DLT tasks

Scheduling is now possible for all new DLT tasks.

Removed manual entry of pin codes for DLT tasks

It is no longer possible to enter PIN codes manually for DLT UDS service 38 tasks, and instead requires either fetching PINs from PIE or 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.

Selectable area code for DLT tasks

It is now possible to select area code for DLT UDS service 38 tasks, default is 0x19.

To read more about DLT tasks, click here.

Show whether PINs are available for a vehicle

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.

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.

Vehicle Communication Forwarder now uses SGA

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 via PIE or from file.

In addition to checking if there is a PIN available via the Check PINs button mentioned above, an icon will indicate whether an appropriate PIN is available on the WCUs vehicle.

Only available if Vehicle Communication Forwarder is enabled for the portal.

Raw MRCOM mode for Vehicle Communication Forwarder

In addition to standard MRCOM forwarding via SGA, a VCF can now be configured to instead use raw MRCOM via ethernet.

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.