WICE Wiki v2.97 - User contributions [en]

New features in v2.97

2026-02-20T08:18:11Z

Jonathan.olsson: /* Support for WCU hardened mode. */

== 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 [[The Portal Administrator View#The User Tab|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 [[I/O configurations#Role (Automotive only)|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 [[Alarm#Set Alarm Interval|here]].

== Improvements to Creating/View Mapping on Signal Reader Task ==
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]
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, [[Mappings|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 [[The Portal Administrator View#The Resource Groups Tab|fetching PINs from PIE]] or [[Vehicles#Upload Vehicle pins|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, [[Creating a Task#Diagnostic Log and Trace (DLT)|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.
[[File:Check PINs result.png|thumb|Check PINs result]]
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|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 [[The Portal Administrator View#The Resource Groups Tab|via PIE]] or [[Vehicles#Upload Vehicle pins|from file]].

In addition to checking if there is a PIN available via the Check PINs button mentioned [[New features in v2.97#Show whether PINs are available for a vehicle|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 ==
[[File:MRCOM forwarding mode.png|thumb|MRCOM forwarding]]
[[File:Raw MRCOM.png|thumb|Raw MRCOM]]
In addition to standard MRCOM forwarding via SGA, a [[Vehicle Communication Forwarder|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.

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

New features in v2.97

2026-02-18T12:50:34Z

Jonathan.olsson: /* Create/View mapping on task improvement */

New features in v2.97

2026-02-18T12:30:44Z

Jonathan.olsson: /* Support for WCU hardened mode. */

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

== 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 “wcu_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 [[The Portal Administrator View#The User Tab|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 [[I/O configurations#Role (Automotive only)|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 [[Alarm#Set Alarm Interval|here]].

== Create/View mapping on task improvement ==
[[File:SignalReaderNewView.png|thumb|Signal Reader View Task]]
[[File:SignalReaderCreateMapping.png|thumb|Signal Reader Create Mapping]]
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, [[Mappings|click here]].

New features in v2.97

2026-02-18T12:12:00Z

Jonathan.olsson: /* Support for automatically generating passwords */

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

== Support for WCU hardened mode. ==

== 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 [[The Portal Administrator View#The User Tab|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 [[I/O configurations#Role (Automotive only)|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 [[Alarm#Set Alarm Interval|here]].

== View mapping on task improvement ==
[[File:SignalReaderView.png|thumb|Signal Reader View Task]]
The signal reader task view has been enhanced to show the mapped-from and mapped-to names for improved readability.

Mappings

2025-11-12T13:35:08Z

Jonathan.olsson: /* Automatic Mapping */

=== Overview ===
[[File:Mapping v2.png|thumb|685x685px]]
The ''Mappings for this task'' window is used to configure the connections between logical communication channels (from a signal reader assignment) and the physical buses used in the system. It displays both CAN and LIN channels and allows you to assign them to specific physical buses (WCU/WMU or VCF).
----

=== Left Side – Logical Channels ===
On the '''left side''' of each group, you can see the logical configuration:

* '''Channel:''' The CAN or LIN bus identifier (e.g., CAN1, LIN1).
* '''Speed:''' The communication speed of the bus (e.g., 500 kbit/s for CAN, 9600 bit/s for LIN).
* '''Name:''' The assigned name of the channel.
* '''#Signals:''' Number of signals currently mapped to that bus.
* '''WCU:''' The drop-down menu where you assign the physical bus.

This area represents the buses defined in the signal reader assignment. These are the ''logical'' buses that need to be linked to ''physical'' buses.
----

=== Right Side – Physical Bus Selection ===
On the '''right side''', under the '''WCU''' column, you select the '''physical bus'''.

* The physical bus can belong to a '''WCU, WMU''' or a '''VCF''' channel.
* Selecting the correct WCU ensures that signals are properly routed to the physical communication hardware.
* The syntax for a physical bus is: '''BUSIO:Speed:Name''' (for example: CAN1:500:CAN1).

----

=== Automatic Mapping ===
The system performs '''auto-mapping''' automatically when the window is opened or refreshed.

Auto-mapping works as follows:

# '''Name Matching:''' The tool first tries to match logical and physical buses based on their names.
# '''Bus Number Matching:''' If names don’t match, it attempts to match based on bus numbers.
# '''Speed Requirement:''' The mapping only succeeds if the '''bus speeds''' are identical.

If a match cannot be made, or if an error occurs, a '''red triangle''' appears next to the affected bus.
----

=== Error and Warning Indicators ===
A '''red triangle''' will appear in the following cases:

* The '''bus speed''' does not match between logical and physical buses.
* The selected '''physical bus''' has already been assigned elsewhere. Each physical bus can '''only be used once''' in the mapping.
A yellow triangle will appear in the following cases:

* No physical bus is selected

----

=== Grouping Option ===
In the '''top-right corner''', there is an option to choose whether '''WCUs should be grouped'''.

When grouping is enabled, the system will automatically match WCUs that have:

* The same number of channels,
* The same I/O numbering, and
* The same communication speed.

When groups are created, an '''eye icon''' 👁️ and a '''number''' appear next to the group name.

* Clicking the '''eye icon''' or the '''number''' displays a list of all WCUs included in that group.
* The number indicates how many WCUs are currently part of the group.

This grouping feature helps simplify configuration when working with multiple identical WCUs.
----

=== Buttons ===
At the bottom of the window:

* '''Save:''' Confirms and saves all mappings.
* '''Restore:''' Resets everything to the ''auto-mapped'' state. (Auto-mapping is always performed first when the window opens.)
* '''Close:''' Exits the window without saving changes.

Mappings

2025-11-12T13:33:45Z

Jonathan.olsson:

=== Overview ===
[[File:Mapping v2.png|thumb|685x685px]]
The ''Mappings for this task'' window is used to configure the connections between logical communication channels (from a signal reader assignment) and the physical buses used in the system. It displays both CAN and LIN channels and allows you to assign them to specific physical buses (WCU/WMU or VCF).
----

=== Left Side – Logical Channels ===
On the '''left side''' of each group, you can see the logical configuration:

* '''Channel:''' The CAN or LIN bus identifier (e.g., CAN1, LIN1).
* '''Speed:''' The communication speed of the bus (e.g., 500 kbit/s for CAN, 9600 bit/s for LIN).
* '''Name:''' The assigned name of the channel.
* '''#Signals:''' Number of signals currently mapped to that bus.
* '''WCU:''' The drop-down menu where you assign the physical bus.

This area represents the buses defined in the signal reader assignment. These are the ''logical'' buses that need to be linked to ''physical'' buses.
----

=== Right Side – Physical Bus Selection ===
On the '''right side''', under the '''WCU''' column, you select the '''physical bus'''.

* The physical bus can belong to a '''WCU, WMU''' or a '''VCF''' channel.
* Selecting the correct WCU ensures that signals are properly routed to the physical communication hardware.
* The syntax for a physical bus is: '''BUSIO:Speed:Name''' (for example: CAN1:500:CAN1).

----

=== Automatic Mapping ===
The system performs '''auto-mapping''' automatically when the window is opened or refreshed.

Auto-mapping works as follows:

# '''Name Matching:''' The tool first tries to match logical and physical buses based on their names.
# '''Bus Number Matching:''' If names don’t match, it attempts to match based on bus numbers.
# '''Speed Requirement:''' The mapping only succeeds if the '''bus speeds''' are identical.

If a match cannot be made, or if an error occurs, a '''red triangle (⚠️)''' appears next to the affected bus.
----

=== Error and Warning Indicators ===
A '''red triangle (⚠️)''' will appear in the following cases:

* The '''bus speed''' does not match between logical and physical buses.
* The selected '''physical bus''' has already been assigned elsewhere.

Each physical bus can '''only be used once''' in the mapping.
----

=== Grouping Option ===
In the '''top-right corner''', there is an option to choose whether '''WCUs should be grouped'''.

When grouping is enabled, the system will automatically match WCUs that have:

* The same number of channels,
* The same I/O numbering, and
* The same communication speed.

When groups are created, an '''eye icon''' 👁️ and a '''number''' appear next to the group name.

* Clicking the '''eye icon''' or the '''number''' displays a list of all WCUs included in that group.
* The number indicates how many WCUs are currently part of the group.

This grouping feature helps simplify configuration when working with multiple identical WCUs.
----

=== Buttons ===
At the bottom of the window:

* '''Save:''' Confirms and saves all mappings.
* '''Restore:''' Resets everything to the ''auto-mapped'' state. (Auto-mapping is always performed first when the window opens.)
* '''Close:''' Exits the window without saving changes.

File:Mapping v2.png

2025-11-12T13:33:27Z

Jonathan.olsson:

mapping

New features in v2.96

2025-11-12T13:11:00Z

Jonathan.olsson: /* New expression for UD signals in Signal Reader */

This page gives a brief introduction to new features or changes introduced in version 2.96 of the WICE portal.

== DLT Daemon mode and DLT UDS in parallel ==
The portal now supports creating DLT tasks with daemon mode and UDS service 38 enabled at the same time. This requires WCU software version 2.96.0 or later for the selected WCUs. See [[Creating a Task#Diagnostic Log and Trace (DLT)|Creating a Task#Diagnostic Log and Trace (DLT).]]

== DLT Daemon address via vehicle announcement ==
For WCUs configured for software version 2.96.0 it is possible to get the daemon address via vehicle announcement instead of specifying a daemon address when the task is created. See [[Creating a Task#Diagnostic Log and Trace (DLT)|Creating a Task#Diagnostic Log and Trace (DLT).]]

== Set, View, and Apply Default WCU Configurations ==
Starting from version 2.96, users can now set, view, and apply default WCU configurations. Admin permissions are required to access these new functions. Read more about it [[Default WCU Configuration|here]].

== Users can now shelve a WCU directly from the Vehicles panel ==
Users with WCU shelving permissions can now shelve a WCU directly in the Vehicles panel. Read more about it [[Shelve and Unshelve a WCU|here]].

== VINReader option to not request VIN if known ==
A new option is available to silence VINReader on startup if the VIN is already known. When in play, VINReader will stay silent, i.e. not request any VIN, if VIN is already known. However, if VIN is unknown, VINReader will send a request for VIN.

== Support for diagnostic Build ID request ==
Starting with version 2.96, the Build ID can serve as the software version identifier. The specific request used as the software version identifier can be configured individually for each vehicle.

== Diagnostic tester detection ==
For WCUs configured for version 2.96.0 and up, it is now possible to set whether to use 'diagnostic tester detection' in the [[I/O configurations#The Miscellaneous Section|IO tab]] when editing the configuration.

== Edit and remove ECU SW from validation for M-Log, Arcos, and IPEmotion RT tasks ==
When viewed in the tasks panel it is now possible to add, edit, or remove ECU SW from validation on [[Creating a Task#M-Log|M-Log]], [[Creating a Task#Arcos|Arcos]], or [[Creating a Task#IPEmotion RT|IPEmotion RT]] tasks.

== Support for configurable PIN codes in sequence files for IDC and Signal Reader ==
If PIC codes have been configured for one or more ECUs in a vehicle connected to a WCU, the PIN codes can be used in diagnostic sequence files in IDC and Signal Reader (DRECs) by referring to the using the naming convention "PIN_<ecuname>_<area>". The name should be prefixed by a dollar sign to indicate that it is a variable name. For example, the PIN code for area 17 in the ECM ECU can be referenced in a sequence file by $PIN_ECM_17. Note that the area code should be hexadecimal.

== New trigger expression operator in Signal Reader ==
Signal Reader has a new trigger expression operator TIME_SINCE_UPDATE, which returs the time in seconds since a specified signal was updated.

== New expression for UD signals in Signal Reader ==
IF-THEN-ELSE expressions are now supported in User Defined signals in Signal Reader.

== Mapping LIN buses on Signal Reader task ==
Support for mapping LIN buses on Signal Reader task. Read more [[Mappings|here.]]

New features in v2.95

2025-08-29T12:48:19Z

Jonathan.olsson: /* Support to view the history of how an assignment has evolved */

== Improved support for uploading a vehicle import file ==
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.

== DLT tasks for strict resource groups ==
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]]. Read more about uploading PINs [[Vehicles#Upload Vehicle pins|here]].

== Compare WCU configurations ==
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the [[Vehicles#Right click context menu|right-click menu]] on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.

== Improved WCU state change search in WCU history ==
It is now possible to search for state transitions in the WCU history panel. For example, searching for a transition from ''In Operation'' to ''Shelving in Progress'' will return all instances where this change occurred. Read more about it [[Vehicles#Right click context menu|here.]]

== New NO_SIGNAL operator for signal reader assignments ==
A new operator, '''NO_SIGNAL('Signal', 'Numeric Value')''', is now available for signal reader trigger expressions. This expression is true if the specified signal has not appeared for at least the specified number of seconds.

== Support to view the history of how an assignment has evolved ==
Support for viewing historical versions has been added to the Assignment Editor for Signal Reader, IDC, and Area5 assignments. When an assignment is open, simply click the new History button to access a list of its saved versions. This list includes the name, date, and editor for each version. You can even click on any of the entries to view the assignment as it existed at that specific point in time. Read more [[Assignment Editor#Assignment History|here.]]

== Support for saving a historical assignment ==
You can now save historical or read-only assignments as a new version. This feature allows you to use a previous assignment as a template, even if you don't have editing permissions for the original. When you '''Save As''', you can give the assignment a new name, and you'll be set as the creator, with full editing permissions for your new copy.

== Possible to delete multiple assignments ==
You can now select multiple lines in the assignment editor and delete them at once. Simply highlight the lines you want to remove and press the delete button.

Assignment Editor

2025-08-29T12:47:32Z

Jonathan.olsson: /* Manage saved assignments */

[[File:Assignment editor v3.png|none|thumb|938x938px]]
This panel is for managing assignments. In this version it is signal reader, Area5 and IDC assignments that are possible to handle. Here you can view, edit and copy saved assignments and create a new one. This window will initially not show any assignment and you need to search or click on “Refresh”. If you are only interested in one type of assignment you can select the specific type at the “Type” column. Which columns that are visible can be managed with the views button in the bottom right of the table. Read more about views [[Save View and Search Expressions|here]]. When selecting an assignment in the table the right panel will show a summary of the assignment.

Read more about specific assignment:

* [[Area5 Assignment Editor|Area5 Assignment]]
*[[Signal Reader Assignment Editor|Signal Reader Assignment]]
*[[IDC Assignment Editor|IDC Assignment]]

==Create a new assignment==
To create a new assignment, click on the “new” button. Then a new Tab shows up where you select the necessary things to create a new assignment.
[[File:NewAssignment.png|none|thumb]]

*Left panel you select type of assignment and which A2L files to use (This option will only be possible if the vehicle profile has any A2L files).
*Center panel you sort and select the vehicle profile to use.
*Right panel will show a summary of how the assignment will be. Please note that this will first be visible when a vehicle profile is selected.

To create the assignment click on "Create assignment".

== Manage saved assignments==

===Edit assignment===
Select an assignment in the listgrid. Then click Edit and a new tab with the assignment will appear. Manage the assignment after click save if you want to save the changes.

===Copy assignment===
Select an assignment in the listgrid. Then click Copy and a new tab like creating assignment will appear. Manage the copy assignment like creating a new one except you have to choose a new name for the assignment.

===Delete assignment ===
Select an assignment in the listgrid. Then click Remove and the assignment will be removed.

=== Import/Export assignment ===
Possible to export and import assignments between different portals. This is only available for signal reader assignments.

* Export: Select an assignment and click on export
* Import: Click on import. Add the .zip file and select a vehicle profile

Read more about signal reader import/export [[Signal Reader Assignment Editor#Import/Export assignment|here.]]

== Assignment running in task==
Assignments that are running on a WCU already are also possible to see. Do the following:

# Go to the Task panel.
# Select a task of the type Area5, IDC or Signal Reader.
# Click View Task and then click on view in assignment editor.

== Assignment History ==
To view the history of a specific assignment, follow these steps:

# Open the desired assignment in the Assignment Editor.
# Locate and click the '''"History"''' button in the down left corner of the editor window.

==== The History Panel ====
Clicking the "History" button will open a new panel, displaying a chronological list of all saved versions of the assignment. Change order in the top left corner. The list provides key information for each version, making it easy to identify the desired historical save:

* '''Name:''' The name of the assignment at the time of saving.
* '''Date:''' The exact date and timestamp when the assignment was saved.
* '''Editor:''' The name of the user who performed the save action.

==== Viewing and Saving a Historical Assignment ====
To view a specific historical version of the assignment, simply click on the open button in the history list. The editor will then load that version, allowing you to review it.

* '''To create a new assignment based on a historical version:''' If you want to use a past version as a template, you can use the '''Save As''' function from the historical view. This is a powerful feature for branching off old configurations without altering the original assignment. It allows you to create a new, editable copy of the assignment with a new name. The new assignment will be owned by you, giving you full editing and saving permissions, regardless of your permissions for the original historical or read-only version.

== Assignment review ==
In the lower right part of the assignment editor start view, there is support to require other users to do a review of an assignment in order to improve the quality of the created assignments. Read more about that process [[Review assignment process|here]].

== Assignment permissions ==
You can set permissions for assignments to control who can edit or remove them. In the “Public/Private” column, you'll see whether the assignment is public or private, and in the “Can Edit” column, you’ll see if the logged-in user has permission to edit the assignment. Only the admin or the owner of the assignment can manage permissions.

If you don’t have permission to edit an assignment, you can still click "Edit" to view the assignment, but you won’t be able to make changes or save it.
[[File:AssignmentPermssion.png|none|thumb|679x679px|Manage permissions]]

=== To Set Permissions: ===

# Search for and select an assignment.
# Click on "Permissions" at the bottom of the page.
# Select Private in the checkbox to make the assignment private. (Unselect the checkbox to make it public again).
# Add users by clicking on “Add” at the bottom of the list. Users listed in the “Can Edit” section will be able to edit the assignment.
# Click Save to apply the changes and set the permissions.

=== User roles: ===
To give more control over a users permission, roles can be configure. Roles can be found by navigating to Administrator -> Users -> Edit Roles and Permissions.

In this section, you can define whether a role has read and/or write access to public and/or private assignments.

You can, for example, give a user permission in a role to write only on private assignments and read on both public and private.

In this way, you can restrict specific users from editing public assignments and allow them to handle only private assignments where they are explicitly listed.

New features in v2.95

2025-08-29T07:35:07Z

Jonathan.olsson: /* Support to view the history of how an assignment has evolved */

== Improved support for uploading a vehicle import file ==
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.

== DLT tasks for strict resource groups ==
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]]. Read more about uploading PINs [[Vehicles#Upload Vehicle pins|here]].

== Compare WCU configurations ==
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the [[Vehicles#Right click context menu|right-click menu]] on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.

== Improved WCU state change search in WCU history ==
It is now possible to search for state transitions in the WCU history panel. For example, searching for a transition from ''In Operation'' to ''Shelving in Progress'' will return all instances where this change occurred. Read more about it [[Vehicles#Right click context menu|here.]]

== New NO_SIGNAL operator for signal reader assignments ==
A new operator, '''NO_SIGNAL('Signal', 'Numeric Value')''', is now available for signal reader trigger expressions. This expression is true if the specified signal has not appeared for at least the specified number of seconds.

== Support to view the history of how an assignment has evolved ==
Support for viewing historical versions has been added to the Assignment Editor for Signal Reader, IDC, and Area5 assignments. When an assignment is open, simply click the new History button to access a list of its saved versions. This list includes the name, date, and editor for each version. You can even click on any of the entries to view the assignment as it existed at that specific point in time.

== Support for saving a historical assignment ==
You can now save historical or read-only assignments as a new version. This feature allows you to use a previous assignment as a template, even if you don't have editing permissions for the original. When you '''Save As''', you can give the assignment a new name, and you'll be set as the creator, with full editing permissions for your new copy.

== Possible to delete multiple assignments ==
You can now select multiple lines in the assignment editor and delete them at once. Simply highlight the lines you want to remove and press the delete button.

New features in v2.95

2025-08-29T07:27:18Z

Jonathan.olsson: /* Support for saving a historical assignment */

== Improved support for uploading a vehicle import file ==
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.

== DLT tasks for strict resource groups ==
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]]. Read more about uploading PINs [[Vehicles#Upload Vehicle pins|here]].

== Compare WCU configurations ==
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the [[Vehicles#Right click context menu|right-click menu]] on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.

== Improved WCU state change search in WCU history ==
It is now possible to search for state transitions in the WCU history panel. For example, searching for a transition from ''In Operation'' to ''Shelving in Progress'' will return all instances where this change occurred. Read more about it [[Vehicles#Right click context menu|here.]]

== New NO_SIGNAL operator for signal reader assignments ==
A new operator, '''NO_SIGNAL('Signal', 'Numeric Value')''', is now available for signal reader trigger expressions. This expression is true if the specified signal has not appeared for at least the specified number of seconds.

== Support to view the history of how an assignment has evolved ==

== Support for saving a historical assignment ==
You can now save historical or read-only assignments as a new version. This feature allows you to use a previous assignment as a template, even if you don't have editing permissions for the original. When you '''Save As''', you can give the assignment a new name, and you'll be set as the creator, with full editing permissions for your new copy.

== Possible to delete multiple assignments ==
You can now select multiple lines in the assignment editor and delete them at once. Simply highlight the lines you want to remove and press the delete button.

Signal Reader Trigger Expressions

2025-08-29T07:23:19Z

Jonathan.olsson:

Trigger conditions are expressions evaluated by the Signal Reader module to control when recorders are started and stopped and when measurement set-up switches are performed.
Trigger conditions are boolean expressions, evaluated to either true or false. A number of operators can be combined to form the trigger expression. The allowed operators in trigger expressions are shown in the table below.

{| class="wikitable"
!=
|Tests for equality. Syntax: expression = expression
|-
!!=
|Tests for inequality. Syntax: expression != expression
|-
!<
|Tests for left side of expression being less than right side. Syntax: expression < expression
|-
!>
|Tests for left side of expression being greater than right side. Syntax: expression > expression
|-
!<=
|Tests for left side of expression being less or equal to right side. Syntax: expression <= expression
|-
!>=
|Tests for left side of expression being greater or equal to right side. Syntax: expression >= expression
|-
!AND
|Logical conjunction between left and right side boolean expressions. Syntax: boolean expression AND boolean expression
|-
!OR
|Logical disjunction between left and right side boolean expressions. Syntax: boolean expression OR boolean expression
|-
!NOT
|Logical negation of boolean expression. Syntax: NOT(boolean expression)
|-
!CHANGE
|True when the specified signal changes value by at least the specified amount. Syntax: CHANGE(Signal, amount)
|-
!CHANGE_UP
|True when the specified signal increases its value with at least the specified amount. Syntax: CHANGE_UP(Signal, amount)
|-
!CHANGE_DOWN
|True when the specified signal decreases its value with at least the specified amount. Syntax: CHANGE_DOWN(Signal, amount)
|-
!CHANGE_BY
|True when the specified signal changes value by exactly the specified amount. Syntax: CHANGE_BY(Signal, amount)
|-
!CHANGE_UP_BY
|True when the specified signal increases its value by exactly the specified amount. Syntax: CHANGE_UP_BY(Signal, amount)
|-
!CHANGE_DOWN_BY
|True when the specified signal decreases its value by exactly the specified amount. Syntax: CHANGE_DOWN_BY(Signal, amount)
|-
!CHANGE_FROM_TO
|True when the specified signal changes from the specified value to the other specified value. Syntax: CHANGE_FROM_TO(Signal, value, value)
|-
!TIMER
|Effects a delay in seconds from that the specified signal is greater than zero. Syntax: TIMER(signal, time)
|-
!EXPR_TIMER
|Effects a delay in seconds from that the condition is fulfilled. Syntax: EXPR_TIMER(expression, time)
|-
!TIME_COUNTER
|Counts the time elapsed while the supplied boolean expression has been true. You can optionally supply an expression resetting the time counter to zero. Syntax: TIME_COUNTER(expression) or TIME_COUNTER(expression, expression)
|-
!SAMPLE_COUNTER
|Counts the number of samples received while the boolean expression is true. You can optionally supply an expression resetting the time counter to zero. Syntax: SAMPLE_COUNTER(expression) or SAMPLE_COUNTER(expression, expression)
|-
!EVERY
|Repeatedly becomes true after a time interval, specified in seconds, has elapsed. Syntax: EVERY(time)
|-
!MOVAV
|Calculates a moving average over the specified signal. Syntax: MOVAV(Signal)
|-
!ABS
|Calculates the absolute value of the specified expression. Syntax: ABS(expression)
|-
!MIN
|Calculates the minimum value of two expressions. Syntax: MIN(expression, expression)
|-
!MAX
|Calculates the maximum value of two expressions. Syntax: MAX(expression, expression)
|-
!MEAN
|Calculates the mean value of two expressions. Syntax: MEAN(expression, expression)
|-
!LOSS_OF_SIGNAL
|True when the specified signal disappears for the specified number of seconds. Syntax: LOSS_OF_SIGNAL(Signal, seconds)
|-
!NO_SIGNAL
|True when the specified signal has not appeared for at least the specified number of seconds. Syntax: NO_SIGNAL('Signal', 'Numeric Value')
|}

New features in v2.95

2025-08-29T07:02:26Z

Jonathan.olsson: /* New NO_SIGNAL operator for signal reader assignments */

== Improved support for uploading a vehicle import file ==
The [[The Portal Administrator View#Upload a Vehicle Import File|CSV import]] has gotten an upgrade, and now handles diagnostics files, vehicle profiles, and labels. It's also more robust, and gives better error messages.

== DLT tasks for strict resource groups ==
DLT tasks have now been expanded to work for strict resource groups. Additionally, when 'Use vehicle specific PINs' is checked in UDS mode it is now be possible to do a check to see if any PINs for the specified ECUs are missing in the portal. The 'Check PINs' feature is currently only available for resource groups. Read more about creating a DLT task [[Creating a Task#Diagnostic Log and Trace (DLT)|here]]. Read more about uploading PINs [[Vehicles#Upload Vehicle pins|here]].

== Compare WCU configurations ==
[[File:Compare WCU configurations - menu.png|thumb|Compare WCU configurations from menu]]
[[File:Compare WCU configurations - selections.png|thumb|Compare WCU configurations selections]]
[[File:Compare WCU configurations - result.png|thumb|WCU configuration comparison results]]
A previous feature has been to compare a groups configuration with that of its resources. This has now been implemented for individual WCUs as well. Comparing individual WCU configurations is accessible via the [[Vehicles#Right click context menu|right-click menu]] on a selected WCU in the [[Vehicles|vehicles tab]]. From there you open a dialog where you can select multiple other WCUs to compare against the current WCU. Pressing 'Compare' will then open a result panel displaying the differing configuration variables for each of the selected WCUs.

== Improved WCU state change search in WCU history ==
It is now possible to search for state transitions in the WCU history panel. For example, searching for a transition from ''In Operation'' to ''Shelving in Progress'' will return all instances where this change occurred. Read more about it [[Vehicles#Right click context menu|here.]]

== New NO_SIGNAL operator for signal reader assignments ==
A new operator, '''NO_SIGNAL('Signal', 'Numeric Value')''', is now available for signal reader trigger expressions. This expression is true if the specified signal has not appeared for at least the specified number of seconds.

== Support to view the history of how an assignment has evolved ==

== Support for saving a historical assignment ==

== Possible to delete multiple assignments ==
You can now select multiple lines in the assignment editor and delete them at once. Simply highlight the lines you want to remove and press the delete button.

New features in v2.95

2025-08-29T06:58:01Z

Jonathan.olsson: /* Possible to delete multiple assignments */

New features in v2.95

2025-08-28T14:05:17Z

Jonathan.olsson: /* Support to view the history of how an assignment has evolved */

New features in v2.95

2025-08-28T14:01:42Z

Jonathan.olsson: /* Support to view the history of how a specific assignment has evolved */

Assignment Editor

2025-06-13T07:42:11Z

Jonathan.olsson:

[[File:Assignment editor v3.png|none|thumb|938x938px]]
This panel is for managing assignments. In this version it is signal reader, Area5 and IDC assignments that are possible to handle. Here you can view, edit and copy saved assignments and create a new one. This window will initially not show any assignment and you need to search or click on “Refresh”. If you are only interested in one type of assignment you can select the specific type at the “Type” column. Which columns that are visible can be managed with the views button in the bottom right of the table. Read more about views [[Save View and Search Expressions|here]]. When selecting an assignment in the table the right panel will show a summary of the assignment.

Read more about specific assignment:

* [[Area5 Assignment Editor|Area5 Assignment]]
*[[Signal Reader Assignment Editor|Signal Reader Assignment]]
*[[IDC Assignment Editor|IDC Assignment]]

==Create a new assignment==
To create a new assignment, click on the “new” button. Then a new Tab shows up where you select the necessary things to create a new assignment.
[[File:NewAssignment.png|none|thumb]]

*Left panel you select type of assignment and which A2L files to use (This option will only be possible if the vehicle profile has any A2L files).
*Center panel you sort and select the vehicle profile to use.
*Right panel will show a summary of how the assignment will be. Please note that this will first be visible when a vehicle profile is selected.

To create the assignment click on "Create assignment".

== Manage saved assignments==

===Edit assignment===
Select an assignment in the listgrid. Then click Edit and a new tab with the assignment will appear. Manage the assignment after click save if you want to save the changes.

===Copy assignment===
Select an assignment in the listgrid. Then click Copy and a new tab like creating assignment will appear. Manage the copy assignment like creating a new one except you have to choose a new name for the assignment.

===Delete assignment ===
Select an assignment in the listgrid. Then click Remove and the assignment will be removed.

=== Import/Export assignment ===
Possible to export and import assignments between different portals. This is only available for signal reader assignments.

* Export: Select an assignment and click on export
* Import: Click on import. Add the .zip file and select a vehicle profile

Read more about signal reader import/export [[Signal Reader Assignment Editor#Import/Export assignment|here.]]

== Assignment running in task==
Assignments that are running on a WCU already are also possible to see. Do the following:

# Go to the Task panel.
# Select a task of the type Area5, IDC or Signal Reader.
# Click View Task and then click on view in assignment editor.

== Assignment review ==
In the lower right part of the assignment editor start view, there is support to require other users to do a review of an assignment in order to improve the quality of the created assignments. Read more about that process [[Review assignment process|here]].

== Assignment permissions ==
You can set permissions for assignments to control who can edit or remove them. In the “Public/Private” column, you'll see whether the assignment is public or private, and in the “Can Edit” column, you’ll see if the logged-in user has permission to edit the assignment. Only the admin or the owner of the assignment can manage permissions.

If you don’t have permission to edit an assignment, you can still click "Edit" to view the assignment, but you won’t be able to make changes or save it.
[[File:AssignmentPermssion.png|none|thumb|679x679px|Manage permissions]]

=== To Set Permissions: ===

# Search for and select an assignment.
# Click on "Permissions" at the bottom of the page.
# Select Private in the checkbox to make the assignment private. (Unselect the checkbox to make it public again).
# Add users by clicking on “Add” at the bottom of the list. Users listed in the “Can Edit” section will be able to edit the assignment.
# Click Save to apply the changes and set the permissions.

=== User roles: ===
To give more control over a users permission, roles can be configure. Roles can be found by navigating to Administrator -> Users -> Edit Roles and Permissions.

In this section, you can define whether a role has read and/or write access to public and/or private assignments.

You can, for example, give a user permission in a role to write only on private assignments and read on both public and private.

In this way, you can restrict specific users from editing public assignments and allow them to handle only private assignments where they are explicitly listed.

File:Assignment editor v3.png

2025-06-13T07:31:52Z

Jonathan.olsson:

assignment editor v3

New features in v2.94

2025-06-12T12:51:12Z

Jonathan.olsson: /* Improved assignment editor permission */

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable Tester address for sigread, idc, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Panel ==

== Support for SOVD IP Address in edit configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'Sovd IP Address' field located under the Connection tab in the Edit Configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit from.

== Support for new platform Kvaser ==
There is support for a new platform called Kvaser.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==
You can now view the frame name for both CAN and LIN signals directly within the "Add Signal" dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.

== Improved assignment editor permission ==
We've upgraded the assignment permission settings to give more control.

Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more [[Assignment Editor#Assignment permissions|here]].

== Improved handling of copy assignment ==
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.

The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

== Support to search for empty values in label columns ==
You can now search for the absence of values in your label columns in various places.

== Cyber security settings ==
For the WCU a bunch of cyber security settings are available.

* Disable USB ethernet interfaces
* Lock signal reader pub/sub communication to localhost
* Disable the SSH daemon
* Root password checks to prevent too weak passwords

New features in v2.94

2025-06-12T12:40:24Z

Jonathan.olsson: /* New assignment editor permission */

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable Tester address for sigread, idc, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Panel ==

== Support for SOVD IP Address in edit configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'Sovd IP Address' field located under the Connection tab in the Edit Configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit from.

== Support for new platform Kvaser ==
There is support for a new platform called Kvaser.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==
You can now view the frame name for both CAN and LIN signals directly within the "Add Signal" dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.

== Improved assignment editor permission ==
We've upgraded the assignment permission settings to give more control.

Previously, assignments could only be marked as private or public. Now, you can assign user-specific permissions to allowing selected users to access private, public, or both types of assignments. Read more here.

== Improved handling of copy assignment ==
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.

The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

== Support to search for empty values in label columns ==
You can now search for the absence of values in your label columns in various places.

== Cyber security settings ==
For the WCU a bunch of cyber security settings are available.

* Disable USB ethernet interfaces
* Lock signal reader pub/sub communication to localhost
* Disable the SSH daemon
* Root password checks to prevent too weak passwords

New features in v2.94

2025-06-12T11:34:21Z

Jonathan.olsson: /* Improved handling of copy assignment */

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable Tester address for sigread, idc, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Panel ==

== Support for SOVD IP Address in edit configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'Sovd IP Address' field located under the Connection tab in the Edit Configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit from.

== Support for new platform Kvaser ==
There is support for a new platform called Kvaser.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==
You can now view the frame name for both CAN and LIN signals directly within the "Add Signal" dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.

== New assignment editor permission ==

== Improved handling of copy assignment ==
We’ve improved the Signal Reader Assignment copy functionality in the Assignment Creator.

The new version ensures a more reliable experience when duplicating assignments and preventing the process from getting stuck.

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

== Support to search for empty values in label columns ==
You can now search for the absence of values in your label columns in various places.

== Cyber security settings ==
For the WCU a bunch of cyber security settings are available.

* Disable USB ethernet interfaces
* Lock signal reader pub/sub communication to localhost
* Disable the SSH daemon
* Root password checks to prevent too weak passwords

New features in v2.94

2025-06-12T11:24:17Z

Jonathan.olsson: /* Frame names in add signals for assignment editor */

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable Tester address for sigread, idc, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Panel ==

== Support for SOVD IP Address in edit configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'Sovd IP Address' field located under the Connection tab in the Edit Configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit from.

== Support for new platform Kvaser ==
There is support for a new platform called Kvaser.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==
You can now view the frame name for both CAN and LIN signals directly within the "Add Signal" dialog for a recorder. Additionally, you can also bring out frame names for signals in the recorder by simple right clicks and select the column “Frame name”.

== New assignment editor permission ==

== Improved handling of copy assignment ==

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

== Support to search for empty values in label columns ==
You can now search for the absence of values in your label columns in various places.

== Cyber security settings ==
For the WCU a bunch of cyber security settings are available.

* Disable USB ethernet interfaces
* Lock signal reader pub/sub communication to localhost
* Disable the SSH daemon
* Root password checks to prevent too weak passwords

New features in v2.94

2025-06-12T07:38:39Z

Jonathan.olsson: /* Support for show signal info for all signals in assignment editor */

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable Tester address for sigread, idc, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Panel ==

== Support for SOVD IP Address in edit configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'Sovd IP Address' field located under the Connection tab in the Edit Configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit.

== Support for new platform Kvaser ==
There is support for a new platform called Kvaser.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==

== New assignment editor permission ==

== Improved handling of copy assignment ==

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

== Support to search for empty values in label columns ==
You can now search for the absence of values in your label coulmns in various places.

New features in v2.94

2025-06-12T07:36:57Z

Jonathan.olsson: /* New assignment editor permission */

== Support for labels in vehicle templates ==
As of version 2.94.0, the Vehicle Template panel supports adding labels to vehicle templates. Read more about it [https://wiki.alkit.se/wice294/index.php/Vehicle_templates here].

== Extend WCU history to account for more changes ==
Two new columns have been added to the WCU history: '''"Type of Change"''' and '''"State"'''.

* '''Type of Change''' indicates whether the update involved a configuration change, a tools change, or a label change.
* '''State''' reflects the WCU’s status at the time of the change, such as "In Operation".

You can read more about these updates [https://wiki.alkit.se/wice294/index.php/Vehicles#Right_click_context_menu here].

== Configurable Tester address for sigread, idc, SoH and vinreader ==
The SignalReader, IDC, State of Health, and VINReader modules have all been updated to include a new field called 'Tester Address.' In the VINReader module, this field is visible only when the ID reader method is set to SPA 29. Additionally, the Tester Address field is available only with WCU version 2.94.0 or later. Read more about it [https://wiki.alkit.se/wice294/index.php/The_Portal_Administrator_View#Configure_the_Vinreader_Module here]

== Fetch PINs from PIE ==

== New column for WCU state in Vehicles Panel ==

== Support for SOVD IP Address in edit configuration ==
As of version 2.94.0, you can enter either an IPv4 address or a physical ID in the 'Sovd IP Address' field located under the Connection tab in the Edit Configuration settings. This field is only visible when the WCU is running version 2.94.0 or later. This is only enabled for customers needing support for the function.

== Support to update a subset of WCU configuration variables ==
[[File:UpdateSubSetOfWCUConfigruationVariable.png|thumb|Update a subset of WCU configuration variables window]]
You can now edit the configuration of multiple WCUs simultaneously. When doing so, the same configuration editor will appear, but with a few new additions. A new '''"Show Changed Settings"''' button allows you to easily track any modifications you've made. Additionally, a new dropdown menu labeled '''"Settings from WCU"''' lets you select which WCU’s configuration you want to edit.

== Support for new platform Kvaser ==
There is support for a new platform called Kvaser.

== Support for admins to download description files. ==
[[File:New-dowload-desc-files.png|thumb|Download description file|200x200px|none]]
If you are an admin and the function is turned on, you have the opportunity to download the vehicle description files found in Administration->Vehicle Profiles panel.

== New alarm when a shelved WCU tries to connect with a vehicle ==
An alarm is raised when a WCU is in any of its shelved states and tries to connect with a vehicle. The category is 'wcu::state::shelved::connect'.

== Support for show signal info for all signals in assignment editor ==

== Frame names in add signals for assignment editor ==

== New assignment editor permission ==

== Support to see when a label was associated with a resource ==
[[File:New label viewer.png|thumb|101x101px|New label viewer]]
There is now support to see at what time a specific label was associated with a resource.

New features in v2.93

2025-03-10T14:16:28Z

Jonathan.olsson: /* Assignment editor improvement */

== Support for using labels to control permissions ==
It is now possible to select resources by labels as an alternative to select resources manually when selecting resources for a permission in [[Roles and permissions]].
[[File:Labels in permissions1.png|thumb|none]]
[[File:Permission label2.png|thumb|Select resources by labels|none]]
When a label is selected as in the screenshot, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels.

After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.

== Support for impersonating another user ==
[[File:Impersonate user.png|thumb|Impersonate user|none]]
An admin user can impersonate another user by selecting a user in the [[The Portal Administrator View#The_User_Tab]] and click the new button "Impersonate" as can be seen in the screenshot "Impersonate user".
[[File:Impersonating user.png|thumb|Impersonating user|none]]
When the button has been clicked, the portal will be reloaded and once logged in again you are now impersonating the selected user. See screenshot "Impersonating user".

To stop impersonating, one can either click the new "Stop impersonating user" icon next to the red text "Impersonating user" or click the logout icon in the upper right corner of the portal.

== Platform types in WMUs ==
[[File:Selected platform for new WMU.png|thumb|Select platform for new WMU|none]]
When adding a new WMU via the portal GUI it is now mandatory to select the platform for the new WMU as can be seen in the screenshot "Select platform for new WMU".

If the WMU is running WMU version 3.0.0 or above it will also report its platform back to the portal. In the case the reported platform does not match the selected platform a warning will be shown and the selected platform must be changed to the reported before the WCU configuration can be saved.
[[File:Reported WMU platform does not match selected2.png|thumb|Reported WMU platform does not match selected|none]]
See screenshot "Reported WMU platform does not match selected.

== Support for moving a vehicle to a resource group when applying a vehicle template ==
It is now possible to move a vehicle into a resource group with the help of vehicle templates. For more detailed information on how to use this feature, you can read more [[Vehicle templates|here]].

== Support to update all vehicles to use a specific SDDB/CSV file ==
A new button, "Apply File to All Vehicles", has been added to ECU Diagnostics. This enables users to apply an SDDB/CSV file to all vehicles at once, making the process of updating multiple vehicles easier.[[File:ApplyFileToAllVehicles.png|thumb|Apply File To all Vehicles|none]]
== Support for MDF file recovery after a WCU crash ==
From version 2.93, the WCU can recover Signal Reader measurement data after a crash or similar unexpected shut-down. To enable this, there is a new checkbox called 'Recover MDF files after unexpected shutdowns' in the Signal Reader module settings. If the checkbox is checked and the WCU crashes, MDF signal data will be recovered from the temporary signal data storage on the WCU the next time the WCU is started. The recovered MDF file is uploaded to the WICE back-end. Pre-trig logging is not possible to recover.

== Support for checking missing and invalid VCF PINs in resource groups ==
[[File:Check PINs window.png|thumb|Check for invalid PINs in resource group|none]]
If the portal supports VCF it is now possible from the IO-tab in edit configuration to check which WCUs in a resource group have missing or wrongly uploaded PINs for VCF. This will bring up a window that gives a summary for each WCU in the group that have missing or invalid PINs. WCUs with all valid VCF PINs will not be shown.

== Assignment editor improvement ==
Improvements for Assignment editor:

* When copying an assignment, users can choose to copy permissions as well.
* Vehicle profile information is now displayed at the bottom of all assignment types, indicating whether it is based on the latest vehicle profile.
* Signals can now be pasted into the DAQ list.

== Frame names in result file ==
It is now possible to include frame names in the result file. This option can be enabled in the Modules tab. Keep in mind that enabling this feature will increase the file size. You can read more [[Signal Reader Assignment Editor#Frame names in result file|here]].

== Computed value labels ==
[[File:Create computed value label.png|left|thumb|Create computed value label]]
It's now possible to create labels which will calculate a value when associated with a resource. One usecase is to use a computed label as a resource group default label to keep track of when resources was added to the group.

The following types are available at the moment:

* Current date - the association date in ISO_DATE format.
* Current date time - the association date/time in ISO_DATE_TIME format.

Signal Reader Assignment Editor

2025-03-10T14:10:19Z

Jonathan.olsson: /* Record frames with filter */

The Signal Reader Assignment Editor can be found under the tab '''Assignment''' and allows the user to create new assignments for signal reader directly in the portal. This page will guide you through the basics of using the editor.

==Edit/Create a signal reader assignment==

The first tab that you are presented with is the '''Assignment global settings''' tab where you can add information about the assignment so that you can easily keep track of what this assignment is about. Creator and creation date are both automatically filled in and cannot be changed because of consistency.

Under the '''Measurements''' tab, see Figure "Measurement Setups", you are presented to a table of Measurement Setups and an information window. These measurement setups are the core of a signal reader assignment. They contain '''Triggers''' that activate and deactivate on certain conditions provided by the user. Each trigger can contain a '''Recorder''' that contains a list of certain signals that will be measured when the start condition for the respective trigger is met. A trigger can also be used to act as a '''setup switch'''.[[File:Measurement setup.png|none|thumb|608x608px|Measurement Setups]]
When you feel finished with the assignment you can simply click the '''Save assignment''' button in the lower right corner to save the assignment in its current state.
===Trigger===
To add a trigger to a measurement setup, click the '''plus''' button for the respective measurement setup. This will create a new Trigger in the trigger table in the respective measurement setup and the information window will be filled with new settings for this trigger for you to add. In the window, trigger type can be set to different types: Recorder, Setup switch, Pause diagnostics, Start/stop CCP DAQ, Start/stop XCP DAQ and Upload. With Setup switch you will jump/end/restart when the start condition is met.

Fill out the '''start trigger''' '''condition''' for the trigger. This is easiest to do in the '''Edit expression''' window that you can get to by clicking one of the '''Edit''' buttons. To find a new signal to add a condition for, use the '''Add signal''' button. Here, you can browse all signals available for this assignment. Use the dropdown to browse signals from different can-busses and Wice internal signals. If you want to browse the signals currently in use in the assignment for the selected signal source, check the '''Search in assignment''' box. If you want more information about a signal, select it and click '''More info'''. When you have found the signal you want, double click it or select it and click '''Add signal'''. Now you can use the '''Operators''' list to add a condition for the signal, for example " > 0". When you are satisfied with the start condition, you will notice that the Validate button has a yellow warning symbol on it. This means that the expression is unvalidated, press the button to validate the expression. The buttons icon now either turns red (expression is unvalid) or green (expression is correct). See Figure "Validate Button States" for the different state of the validate button. Click Save to save the expression. The list of operators supported in trigger condition is available [[Signal Reader Trigger Expressions|here]].[[File:ValidateButtonStates.png|thumb|Validate Button States|link=https://wiki.alkit.se/wice264/index.php/File:ValidateButtonStates.png|none]]A '''stop trigger condition''' is not required, but can be supplied to determine when the recording should stop. If the stop condition is not supplied, the settings for the recorder will tell when the recording should stop.
===Recorder===
There a two types of recorder, SREC (Signal recorder) and DREC (Diagnostics recorder). Choose which one you want with the radio button at the top of the Recorder tab.
====Recorder - DREC====
DREC (Diagnostics recorder) is used to send diagnostic requests onto the vehicle's communication buses and record the responses. The diagnostic requests are supplied in a sequence file uploaded by the user. The sequence file contains one diagnostic request per line, with the ECU id at the beginning of the line. There can optionally be other information as well. The syntax is the same as the one used for the IDC module, see [[IDC Sequence File Syntax|Sequence File Syntax]]. The result from a DREC will be a diagnostic log file, a text file containing both the requests from the sequence file and the corresponding responses.

The DREC (Diagnostics Recorder) is a tool used to send diagnostic requests onto the vehicle's communication buses and record the responses. The diagnostic requests can be provided in one of two ways:

# By uploading a sequence file, where:
#* The sequence file contains one diagnostic request per line, with the ECU ID at the beginning of the line. Optionally, additional information may also be included. The syntax used for the sequence file is identical to that of the IDC module; for more details, refer to Sequence File Syntax.
# By selecting an existing IDC assignment.

The output generated by DREC is a diagnostic log file, which is a text file containing both the requests (from the sequence file or IDC assignment) and their corresponding responses.

====Recorder - SREC====
SREC (Signal recorder) is used to record signals on the vehicle's communication buses. The result of an SREC is an MDF file containing the time series data of the selected signals.

For signal recorder there is 3 tabs:

* Symbols - Add/Remove/view signals to record
* Frames - Handle frame recorder on Passive CAN and Flexray busses.
* Properties - Settings for the recorder.

===== Symbols: =====
Buttons on the bottom strip:

* Add Signal: Will open a window where signals can be added from. By selecting a signal source the list will be populated with signals available from that source.
* Remove selected: Selected signals will be removed. This is also possible by right click on the list.
* Edit Selected: To edit PLA-compressions (Read more [[PLA-compression window|here]].) and skip factor. Skip factor will be applied to all selected signals.
* More info: Shows more info about passive and Flexrays signals.
* Upload text file with signals names. If the signal does not have a module name it is expected to belong to the already selected signal source/module.
* Paste signals name to be added. If the signal does not have a module name it is expected to belong to the already selected signal source/module.
* Copy signals. In the new window it is possible to switch if it is only the filtered or all signals copied.
[[File:Srec.png|none|thumb|955x955px]]

====== Add Signals: ======
Click on the '''Add Signal''' button to show the window. Select modules/signal source and search up the signals that you want to add. Select those signals and click on "Add signals".
=====Recorder - Properties=====
Under the recorder tab '''Properties''' you can select the properties for the recorder, see Figure "Recorder Properties".

'''Number of shots''' is an important factor for a recorder. A '''shot''' is the term used for a single recording and number of shots is therefore the number of times we should record. A shot is only started when the start trigger condition is met and will continue until any of these events occur:
*The recording fulfills the maximum duration.
*The recording fulfills the minimum duration and the '''stop trigger condition''' is met.
*The recording fulfills the minimum duration and a trigger start a '''setup switch'''.
*The recording fulfills the minimum duration and another recorder starts a '''setup switch'''.
*A setup switch is started manually.
*The assignment is stopped manually.
The '''recorder Setup switch''' is started when recorder has performed its number of shots and all other started recorders have at least fulfilled their minimum duration. It is, like the trigger setup switch, used to switch to/run a measurement setup.

You can also select the '''Pre trigg duration''' which determines the amount of data that will be saved in the flash before the start trigger condition is met. Range is 0 to 2147483647 (231 -1).

The '''Post trigg duration''' is much like the pre trigg duration and determines the amount of data that will be saved after the stop trigger condition is met. Range is 0 to 2147483647 (231 -1).

The '''Minimum duration''' determines the minimum amount of data that needs to be recorded before it becomes possible to cancel the recording through either a stop trigger or a setup swtich started by a trigger or another recorder.

The '''Maximum duration''' determines, as the name suggest, the maximum amount of data that should be recorded. Range is 0 to 2147483647 (231 -1).

The '''Unit''' for the four aforementioned durations can be set to seconds, samples or bytes. If you choose to set them to seconds, the device will use the timestamps of the incoming data to determine the four aforementioned durations.[[File:Recorder properties.png|thumb|600x600px|Recorder Properties|none|link=https://wiki.alkit.se/wice264/index.php/File:Recorder_properties.png]]

== Active signals ==
An Active Signal is a signal that is created by polling an ECU for a numerical value at a predefined frequency. The polling is typically done using the ReadDataByIdentifier diagnostic service. To create an assignment with active signals, the vehicle profile has to have a diagnostic description. This is set in the vehicle profile settings [[Vehicle Pofiles|here]]. There has to be a diagnostic description connected to the vehicle profile when the assignments are created to be able to select active signals. If a vehicle profile is updated, an assignment can be upgraded to match the new vehicle profile by doing a copy. This will automatically upgrade it and if there is a diagnostic description connected it will be possible to use active signals.

Select “Active signal” in signal Source. Then it is possible to select ECU in ECU name. After that available signals will show up and select/deselect works like for the other signal sources.

When creating a task with an assignment that has active signals selected, a button “ECU SW mappings” will show up. If there is a red exclamation mark, a specific software version has to be selected for one or more ECUs. If a recorder signal does not exist in the selected software version it will be removed. Note that the software version has to contain all active signals that exist in the trigger conditions otherwise it will not be possible to create the task.
==Using a portal assignment for a signal reader task==
In order to use a portal assignment. Select the WCUs in the Vehicle tab that you want to create the new signal reader assignment for and click new task. Navigate to the Signal reader tab and click the '''Browse saved assignments''' button and select the assignment you want to use and click '''Ok'''. This assignment will now be used to create the .haf file required by the WCUs to perform the signal reader task. If selecting "Legacy WICE internal signal names" certain wice internal signals names will be translated.
[[File:BrowseSR.png|none|thumb|600x600px|View Assignments]]
Legacy WICE internal signal names:
{| class="wikitable"
! From
!To
|-
|WICE.Longitude
|WICE_Generic_Internal.Longitude_0020
|-
|WICE.Latitude
|WICE_Generic_Internal.Latitude_0020
|-
| WICE.CSQ
| WICE_Generic_Internal.CSQ_0020
|-
|WICE.WCU_Voltage
|WICE_Generic_Internal.WCU_Voltage_0103
|-
|WICE.WCU_Temp
|WICE_Generic_Internal.WCU_Temp_0104
|-
|WICE.Time_Since_Epoch
|WICE_Generic_Internal.Time_Since_Epoch_0090
|-
|WICE.Start_Signal
|WICE_Generic_Internal.Start_Signal_0100
|}
== Select different communication interface or transport protocol ==
Under the "Modules" tab, the different signal sources are visible. In the "I/O" column, the selected communication interface and transport protocol are shown. By selecting a row and then clicking on the button “Edit Interface” this can be changed. Currently this is only possible for modules with type “A2L” or "Diagnostics." When changing this, a validation of the settings with what is red from the corresponding A2L file is done. If the validation is successful, a green icon will appear. If the icon is a red cross the A2L file does not contain the necessary information for the setting.

When selecting between CAN and Ethernet/DoIP diagnostics, a window pops up where you can select the interface between "Default Channel", "CAN" or "DoIP". Selecting "Default Channel" means that the default channel in the signal reader module settings on the wcu is going to be used. Interface "CAN" a specific CAN interface can be selected to be used for the diagnostic requests. If selecting "DoIP", the diagnostics will be performed over Ethernet using the Diagnostics-over-IP (DoIP) protocol. In this case, you can also select whether to use the IP address broadcasted by the vehicle in a "Vehicle Announcement" message, or you can specify the IP address explicitly (in which case the Vehicle Announcement will be ignored). The DoIP port number to use (default 13400) can also be specified.

A2L modules support the following interfaces, CPP-CAN, XCP-CAN, XCP-TCP, XCP-UDP and UDS (2C/2A).[[File:DoIP-ass-ed.png|alt=CAN or DoIP settings|thumb|CAN or DoIP settings|none]]

== Record frames with filter ==
Frame recorder can be used on FlexRay and CAN-bus. In a signal recorder the frame recorder with or without filter can be activated.

To activate/deactivate the frame recorder for a module either click on the active icon or select a specific row and click Toggle.

To edit the filter either double click on row or click on edit filter.
[[File:Framerecorder.png|none|thumb|482x482px]]

== Frame names in result file ==
If frame names should be included in the result file, this option can be enabled in the Modules tab.

First, select the desired CAN bus, then click on 'Toggle Frame Names' or simply check the 'Add Frame Names' column.

'''Note that this will increase the size of the result file.'''

== User defined signals ==
In this tab are user defined signals handled.

* Add and remove signals by clicking the respective button.
* Signals names are set on creation and can not be changed after that.
* Calculation formula is the formula that will be calculated for the signal's value. For example writing “module.signal_name + 10” will increase “signal_name” by 10.
* Update on signals is determining when the formula shall be calculated. Each time that signals get present the new user defined signal will be calculated.

This type of signals can then be used in triggers and recorder by finding the name that will be “UD.<Name>”.
[[File:UD Editor2.png|none|thumb|483x483px]]

== Import/Export assignment ==
Signal reader assignment can be exported and then be imported in another portal. Versions can mismatch with one version and still work. If it differs more, use it carefully. When importing an assignment and vehicle profile needs to be selected. This profile should be similar to that one the original assignment was based on. If some signals or signals source do not exist in the new profile that was used in assignment a warning message will be shown with information about what is missing. If missing signals were used in a trigger expression the state will be set as invalid. Today there is no way to export and import a vehicle profile. So these have to be done manually.

== DAQ/Event-list ==
If the assignment contains signals source that are compatible with DAQ list or Event channels a tab with name “DAQ/Event” will be visible. After signals have been added to the recorder it can be added to the DAQ list.

=== Add new DAQ-List ===
To add a new DAQ list click on green plus icon on specific Measurement setup and ECU name. The new window shows all the DAQ-list that was predefined in the a2l-file. '''NOTE! What information that will be shown depends on what transport protocol that is selected in the module settings.''' If there is no information the table will be empty. Choose either one from the list or select “New blank” to define DAQ-list yourself.
[[File:AddNewDAQ.png|none|thumb|528x528px]]

=== Manage DAQ-List ===
On “Edit DAQ” following settings can be made:

* Name
* DAQ number: Must be unique
* Periodicity: Will not affect the real periodicity is only for information.
* Max bytes/Max Frame: Depending on measurement is over can or ethernet.
* Prescaler

[[File:DAQList.png|none|thumb|542x542px]]

=== Manage Event channel ===
Manage event channels is similar to DAQ-list. In DAQ list you add signals but in event channels you add DAQ-list. With “Edit event” following settings can be made:

* Name
* Channel number: Must be unique.
* Periodicity: Will not affect the real periodicity is only for information.
* Max DAQs: Note that 255 meaning infinity.
* Max Size of DAQs: Max byte each DAQ list can contain.
* Priority

New features in v2.93

2025-03-10T13:34:16Z

Jonathan.olsson: Assignment editor improvement

== Support for using labels to control permissions ==
It is now possible to select resources by labels as an alternative to select resources manually when selecting resources for a permission in [[Roles and permissions]].
[[File:Labels in permissions1.png|thumb|none]]
[[File:Permission label2.png|thumb|Select resources by labels|none]]
When a label is selected as in the screenshot, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels.

After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.

== Support for impersonating another user ==
[[File:Impersonate user.png|thumb|Impersonate user|none]]
An admin user can impersonate another user by selecting a user in the [[The Portal Administrator View#The_User_Tab]] and click the new button "Impersonate" as can be seen in the screenshot "Impersonate user".
[[File:Impersonating user.png|thumb|Impersonating user|none]]
When the button has been clicked, the portal will be reloaded and once logged in again you are now impersonating the selected user. See screenshot "Impersonating user".

To stop impersonating, one can either click the new "Stop impersonating user" icon next to the red text "Impersonating user" or click the logout icon in the upper right corner of the portal.

== Platform types in WMUs ==
[[File:Selected platform for new WMU.png|thumb|Select platform for new WMU|none]]
When adding a new WMU via the portal GUI it is now mandatory to select the platform for the new WMU as can be seen in the screenshot "Select platform for new WMU".

If the WMU is running WMU version 3.0.0 or above it will also report its platform back to the portal. In the case the reported platform does not match the selected platform a warning will be shown and the selected platform must be changed to the reported before the WCU configuration can be saved.
[[File:Reported WMU platform does not match selected2.png|thumb|Reported WMU platform does not match selected|none]]
See screenshot "Reported WMU platform does not match selected.

== Support for moving a vehicle to a resource group when applying a vehicle template ==
It is now possible to move a vehicle into a resource group with the help of vehicle templates. For more detailed information on how to use this feature, you can read more [https://wiki.alkit.se/wice293/index.php/Vehicle_templates here].

== Support to update all vehicles to use a specific SDDB/CSV file ==
A new button, "Apply File to All Vehicles", has been added to ECU Diagnostics. This enables users to apply an SDDB/CSV file to all vehicles at once, making the process of updating multiple vehicles easier.[[File:ApplyFileToAllVehicles.png|thumb|Apply File To all Vehicles|none]]
== Support for MDF file recovery after a WCU crash ==
From version 2.93, the WCU can recover Signal Reader measurement data after a crash or similar unexpected shut-down. To enable this, there is a new checkbox called 'Recover MDF files after unexpected shutdowns' in the Signal Reader module settings. If the checkbox is checked and the WCU crashes, MDF signal data will be recovered from the temporary signal data storage on the WCU the next time the WCU is started. The recovered MDF file is uploaded to the WICE back-end. Pre-trig logging is not possible to recover.

== Support for checking missing and invalid VCF PINs in resource groups ==
[[File:Check PINs window.png|thumb|Check for invalid PINs in resource group|none]]
If the portal supports VCF it is now possible from the IO-tab in edit configuration to check which WCUs in a resource group have missing or wrongly uploaded PINs for VCF. This will bring up a window that gives a summary for each WCU in the group that have missing or invalid PINs. WCUs with all valid VCF PINs will not be shown.

== Assignment editor improvement ==
Improvements for Assignment editor:

* When copying an assignment, users can choose to copy permissions as well.
* Vehicle profile information is now displayed at the bottom of all assignment types, indicating whether it is based on the latest vehicle profile.
* Signals can now be pasted into the DAQ list.

== Computed value labels ==
[[File:Create computed value label.png|left|thumb|Create computed value label]]
It's now possible to create labels which will calculate a value when associated with a resource. One usecase is to use a computed label as a resource group default label to keep track of when resources was added to the group.

The following types are available at the moment:

* Current date - the association date in ISO_DATE format.
* Current date time - the association date/time in ISO_DATE_TIME format.

New features in v2.93

2025-03-06T12:16:29Z

Jonathan.olsson: /* Support for using labels to control permissions */

== Support for using labels to control permissions ==
It is now possible to select resources by labels as an alternative to select resources manually when selecting resources for a permission in [[Roles and permissions]].
[[File:Labels in permissions1.png|thumb|none]]
[[File:Permission label2.png|thumb|Select resources by labels|none]]
When a label is selected as in the screenshot, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels.

After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.

== Support for impersonating another user ==
[[File:Impersonate user.png|thumb|Impersonate user|none]]
An admin user can impersonate another user by selecting a user in the [[The Portal Administrator View#The_User_Tab]] and click the new button "Impersonate" as can be seen in the screenshot "Impersonate user".
[[File:Impersonating user.png|thumb|Impersonating user|none]]
When the button has been clicked, the portal will be reloaded and once logged in again you are now impersonating the selected user. See screenshot "Impersonating user".

To stop impersonating, one can either click the new "Stop impersonating user" icon next to the red text "Impersonating user" or click the logout icon in the upper right corner of the portal.

== Platform types in WMUs ==
[[File:Selected platform for new WMU.png|thumb|Select platform for new WMU|none]]
When adding a new WMU via the portal GUI it is now mandatory to select the platform for the new WMU as can be seen in the screenshot "Select platform for new WMU".

If the WMU is running WMU version 3.0.0 or above it will also report its platform back to the portal. In the case the reported platform does not match the selected platform a warning will be shown and the selected platform must be changed to the reported before the WCU configuration can be saved.
[[File:Reported WMU platform does not match selected2.png|thumb|Reported WMU platform does not match selected|none]]
See screenshot "Reported WMU platform does not match selected.

== Support for moving a vehicle to a resource group when applying a vehicle template ==
It is now possible to move a vehicle into a resource group with the help of vehicle templates. For more detailed information on how to use this feature, you can read more [https://wiki.alkit.se/wice293/index.php/Vehicle_templates here].

== Support for MDF file recovery after a WCU crash ==
[[File:ApplyFileToAllVehicles.png|thumb|Apply File To all Vehicles|none]]
From version 2.93, the WCU can recover Signal Reader measurement data after a crash or similar unexpected shut-down. To enable this, there is a new checkbox called 'Recover MDF files after unexpected shutdowns' in the Signal Reader module settings. If the checkbox is checked and the WCU crashes, MDF signal data will be recovered from the temporary signal data storage on the WCU the next time the WCU is started. The recovered MDF file is uploaded to the WICE back-end. Pre-trig logging is not possible to recover.

== Support for checking missing and invalid VCF PINs in resource groups ==
[[File:Check PINs window.png|thumb|Check for invalid PINs in resource group|none]]
If the portal supports VCF it is now possible from the IO-tab in edit configuration to check which WCUs in a resource group have missing or wrongly uploaded PINs for VCF. This will bring up a window that gives a summary for each WCU in the group that have missing or invalid PINs. WCUs with all valid VCF PINs will not be shown.

New features in v2.93

2025-03-06T12:13:15Z

Jonathan.olsson: /* Support for MDF file recovery after a WCU crash */

== Support for using labels to control permissions ==
It is now possible to select resources by labels as an alternative to select resources manually when selecting resources for a permission in [[Roles and permissions]].
[[File:Labels in permissions1.png|thumb]]
[[File:Permission label2.png|thumb|Select resources by labels]]
When a label is selected as in the screenshot to the right, the WCUs which are currently associated with the label are added to the set of selected resources. Multiple labels can also be used to either collect more resources or narrow down the resources depending on the chosen relation between the labels.

After the permission has been saved, any additional resources which get associated with the labels used in the permission will automatically be added to the permission. Since these labels now controls one or many permissions, only the users with the role admin can add or remove the labels from resources as long as they are part of any permission.

== Support for impersonating another user ==
[[File:Impersonate user.png|thumb|Impersonate user]]
An admin user can impersonate another user by selecting a user in the [[The Portal Administrator View#The_User_Tab]] and click the new button "Impersonate" as can be seen in the screenshot "Impersonate user".
[[File:Impersonating user.png|thumb|Impersonating user]]
When the button has been clicked, the portal will be reloaded and once logged in again you are now impersonating the selected user. See screenshot "Impersonating user".

To stop impersonating, one can either click the new "Stop impersonating user" icon next to the red text "Impersonating user" or click the logout icon in the upper right corner of the portal.

== Platform types in WMUs ==
[[File:Selected platform for new WMU.png|thumb|Select platform for new WMU]]
When adding a new WMU via the portal GUI it is now mandatory to select the platform for the new WMU as can be seen in the screenshot "Select platform for new WMU".

If the WMU is running WMU version 3.0.0 or above it will also report its platform back to the portal. In the case the reported platform does not match the selected platform a warning will be shown and the selected platform must be changed to the reported before the WCU configuration can be saved.
[[File:Reported WMU platform does not match selected2.png|thumb|Reported WMU platform does not match selected]]
See screenshot "Reported WMU platform does not match selected.

== Support for moving a vehicle to a resource group when applying a vehicle template ==
It is now possible to move a vehicle into a resource group with the help of vehicle templates. For more detailed information on how to use this feature, you can read more [https://wiki.alkit.se/wice293/index.php/Vehicle_templates here].

== Support for MDF file recovery after a WCU crash ==
[[File:ApplyFileToAllVehicles.png|thumb|Apply File To all Vehicles]]
From version 2.93, the WCU can recover Signal Reader measurement data after a crash or similar unexpected shut-down. To enable this, there is a new checkbox called 'Recover MDF files after unexpected shutdowns' in the Signal Reader module settings. If the checkbox is checked and the WCU crashes, MDF signal data will be recovered from the temporary signal data storage on the WCU the next time the WCU is started. The recovered MDF file is uploaded to the WICE back-end. Pre-trig logging is not possible to recover.

== Support for checking missing and invalid VCF PINs in resource groups ==
[[File:Check PINs window.png|thumb|Check for invalid PINs in resource group]]
If the portal supports VCF it is now possible from the IO-tab in edit configuration to check which WCUs in a resource group have missing or wrongly uploaded PINs for VCF. This will bring up a window that gives a summary for each WCU in the group that have missing or invalid PINs. WCUs with all valid VCF PINs will not be shown.

New features in v2.92

2024-12-16T16:05:29Z

Jonathan.olsson: /* Support for ICCID in the WCU history panel */

== Support for WiFi on platform HMX/V2 ==
In version 2.92, we have added support for WiFi on the HMX/V2 platform in the WCU configuration panel. To access the WiFi settings, the WCU must be running at least version 2.92.0.

== Support for ICCID in the WCU history panel ==
ICCID is now available in the WCU history panel, enabling users to see which SIM card is installed in the WCU. Read more about it [[Vehicles#Right click context menu|here]].

== Time Limited Remote Logon ==
It is now possible to specify a time limit (in hours) for the remote logon configuration. If specified, the remote logon configuration will be automatically disabled after the limit has expired.

Depending on the portal setup, the following modes are possible:

* None - not possible to specify a time limit.
* Optional - the user may specify a time limit.
* Required - the user must specify a time limit.
Read more about it [[The Portal Administrator View#Remote Login|here]].

== Fetch uploaded Vehicle PINs ==
It is now possible to fetch PINs for HIA, HIB and Diagnostic firewall disable in the IO-tab of the WCU configuration panel. This is done by setting the checkbox 'Fetch Uploaded PINs' which will fetch and apply any available PINs once you save the configuration. For individual WCUs it is also possible to use the 'Get PINs' button to immediately apply the PINs and receive some additional feedback. Resource groups can only fetch PINs via the checkbox. The PINs will be automatically applied to the corresponding fields if available. Read more about fetching PINs [[I/O configurations#The Miscellaneous Section|here]] and [[I/O configurations#Get PINs or Check PINs|here]].

Only PINs that have been uploaded via 'Upload Vehicle PINs' in the vehicles-tab with the correct service area will be fetched. Read more about uploading PINs for individual vehicles [[Vehicles#Right%20click%20context%20menu|here]] and for multiple vehicles [[Vehicles#Upload Vehicle pins|here]].

Requires WCU version 2.89.0 or higher.

== Signal reader assignments support DREC with IDC assignments ==
In signal reader DREC it was previously only possible to upload sequence files. Now you also can select an existing IDC assignment. Read more about DREC [[Signal Reader Assignment Editor#Recorder - DREC|here]].

== Assignment editor now with permissions for edit and remove assignments ==
You can now set permissions for assignments, controlling who can edit or remove them. Admins and owners of the assignment can designate assignments as private or public, and assign edit permissions to specific users. Non-editors can view but not modify assignments. Read more about it [[Assignment Editor#Assignment permissions|here]].

== Support for UDS service 38 for task type DLT ==
It is now possible to get ECU logs using service 38 in addition to using the DLT daemon for DLT tasks. Read more about it [[Creating a Task#Diagnostic Log and Trace (DLT)|here]].

== Support to copy resource group ==
It is now possible to copy a resource group.

New features in v2.92

2024-12-16T16:04:55Z

Jonathan.olsson: /* Time Limited Remote Logon */

== Support for WiFi on platform HMX/V2 ==
In version 2.92, we have added support for WiFi on the HMX/V2 platform in the WCU configuration panel. To access the WiFi settings, the WCU must be running at least version 2.92.0.

== Support for ICCID in the WCU history panel ==
ICCID is now available in the WCU history panel, enabling users to see which SIM card is installed in the WCU. Read more about it [https://wiki.alkit.se/wice292/index.php/Vehicles#Right_click_context_menu here].

== Time Limited Remote Logon ==
It is now possible to specify a time limit (in hours) for the remote logon configuration. If specified, the remote logon configuration will be automatically disabled after the limit has expired.

Depending on the portal setup, the following modes are possible:

* None - not possible to specify a time limit.
* Optional - the user may specify a time limit.
* Required - the user must specify a time limit.
Read more about it [[The Portal Administrator View#Remote Login|here]].

== Fetch uploaded Vehicle PINs ==
It is now possible to fetch PINs for HIA, HIB and Diagnostic firewall disable in the IO-tab of the WCU configuration panel. This is done by setting the checkbox 'Fetch Uploaded PINs' which will fetch and apply any available PINs once you save the configuration. For individual WCUs it is also possible to use the 'Get PINs' button to immediately apply the PINs and receive some additional feedback. Resource groups can only fetch PINs via the checkbox. The PINs will be automatically applied to the corresponding fields if available. Read more about fetching PINs [[I/O configurations#The Miscellaneous Section|here]] and [[I/O configurations#Get PINs or Check PINs|here]].

Only PINs that have been uploaded via 'Upload Vehicle PINs' in the vehicles-tab with the correct service area will be fetched. Read more about uploading PINs for individual vehicles [[Vehicles#Right%20click%20context%20menu|here]] and for multiple vehicles [[Vehicles#Upload Vehicle pins|here]].

Requires WCU version 2.89.0 or higher.

== Signal reader assignments support DREC with IDC assignments ==
In signal reader DREC it was previously only possible to upload sequence files. Now you also can select an existing IDC assignment. Read more about DREC [[Signal Reader Assignment Editor#Recorder - DREC|here]].

== Assignment editor now with permissions for edit and remove assignments ==
You can now set permissions for assignments, controlling who can edit or remove them. Admins and owners of the assignment can designate assignments as private or public, and assign edit permissions to specific users. Non-editors can view but not modify assignments. Read more about it [[Assignment Editor#Assignment permissions|here]].

== Support for UDS service 38 for task type DLT ==
It is now possible to get ECU logs using service 38 in addition to using the DLT daemon for DLT tasks. Read more about it [[Creating a Task#Diagnostic Log and Trace (DLT)|here]].

== Support to copy resource group ==
It is now possible to copy a resource group.

Assignment Editor

2024-12-16T16:01:04Z

Jonathan.olsson: /* Assignment permissions */

[[File:Assignment editor v2.png|none|thumb|944x944px|Assignment Editor start view]]
This panel is for managing assignments. In this version it is signal reader, Area5 and IDC assignments that are possible to handle. Here you can view, edit and copy saved assignments and create a new one. This window will initially not show any assignment and you need to search or click on “Refresh”. If you are only interested in one type of assignment you can select the specific type at the “Type” column. Which columns that are visible can be managed with the views button in the bottom right of the table. Read more about views [[Save View and Search Expressions|here]]. When selecting an assignment in the table the right panel will show a summary of the assignment.

Read more about specific assignment:

* [[Area5 Assignment Editor|Area5 Assignment]]
*[[Signal Reader Assignment Editor|Signal Reader Assignment]]
*[[IDC Assignment Editor|IDC Assignment]]

==Create a new assignment==
To create a new assignment, click on the “new” button. Then a new Tab shows up where you select the necessary things to create a new assignment.
[[File:NewAssignment.png|none|thumb]]

*Left panel you select type of assignment and which A2L files to use (This option will only be possible if the vehicle profile has any A2L files).
*Center panel you sort and select the vehicle profile to use.
*Right panel will show a summary of how the assignment will be. Please note that this will first be visible when a vehicle profile is selected.

To create the assignment click on "Create assignment".

== Manage saved assignments==

===Edit assignment===
Select an assignment in the listgrid. Then click Edit and a new tab with the assignment will appear. Manage the assignment after click save if you want to save the changes.

===Copy assignment===
Select an assignment in the listgrid. Then click Copy and a new tab like creating assignment will appear. Manage the copy assignment like creating a new one except you have to choose a new name for the assignment.

===Delete assignment ===
Select an assignment in the listgrid. Then click Remove and the assignment will be removed.

=== Import/Export assignment ===
Possible to export and import assignments between different portals. This is only available for signal reader assignments.

* Export: Select an assignment and click on export
* Import: Click on import. Add the .zip file and select a vehicle profile

Read more about signal reader import/export [[Signal Reader Assignment Editor#Import/Export assignment|here.]]

== Assignment running in task==
Assignments that are running on a WCU already are also possible to see. Do the following:

# Go to the Task panel.
# Select a task of the type Area5, IDC or Signal Reader.
# Click View Task and then click on view in assignment editor.

== Assignment review ==
In the lower right part of the assignment editor start view, there is support to require other users to do a review of an assignment in order to improve the quality of the created assignments. Read more about that process [[Review assignment process|here]].

== Assignment permissions ==
You can set permissions for assignments to control who can edit or remove them. In the “Public/Private” column, you'll see whether the assignment is public or private, and in the “Can Edit” column, you’ll see if the logged-in user has permission to edit the assignment. Only the admin or the owner of the assignment can manage permissions.

If you don’t have permission to edit an assignment, you can still click "Edit" to view the assignment, but you won’t be able to make changes or save it.
[[File:AssignmentPermssion.png|none|thumb|679x679px|Manage permissions]]

=== To Set Permissions: ===

# Search for and select an assignment.
# Click on "Permissions" at the bottom of the page.
# Select Private in the checkbox to make the assignment private. (Unselect the checkbox to make it public again).
# Add users by clicking on “Add” at the bottom of the list. Users listed in the “Can Edit” section will be able to edit the assignment.
# Click Save to apply the changes and set the permissions.

File:AssignmentPermssion.png

2024-12-16T16:00:29Z

Jonathan.olsson:

assignmentPermssion

New features in v2.92

2024-12-16T15:59:09Z

Jonathan.olsson: /* Assignment editor now with permissions for edit and remove assignments */

== Support for WiFi on platform HMX/V2 ==
In version 2.92, we have added support for WiFi on the HMX/V2 platform in the WCU configuration panel. To access the WiFi settings, the WCU must be running at least version 2.92.0.

== Support for ICCID in the WCU history panel ==
ICCID is now available in the WCU history panel, enabling users to see which SIM card is installed in the WCU. Read more about it [https://wiki.alkit.se/wice292/index.php/Vehicles#Right_click_context_menu here].

== Time Limited Remote Logon ==
It is now possible to specify a time limit (in hours) for the remote logon configuration. If specified, the remote logon configuration will be automatically disabled after the limit has expired.

Depending on the portal setup, the following modes are possible:

* None - not possible to specify a time limit.
* Optional - the user may specify a time limit.
* Required - the user must specify a time limit.
Read more about it [https://wiki.alkit.se/wice292/index.php/The_Portal_Administrator_View#Remote_Login here].

== Fetch uploaded Vehicle PINs ==
It is now possible to fetch PINs for HIA, HIB and Diagnostic firewall disable in the IO-tab of the WCU configuration panel. This is done by setting the checkbox 'Fetch Uploaded PINs' which will fetch and apply any available PINs once you save the configuration. For individual WCUs it is also possible to use the 'Get PINs' button to immediately apply the PINs and receive some additional feedback. Resource groups can only fetch PINs via the checkbox. The PINs will be automatically applied to the corresponding fields if available. Read more about fetching PINs [[I/O configurations#The Miscellaneous Section|here]] and [[I/O configurations#Get PINs or Check PINs|here]].

Only PINs that have been uploaded via 'Upload Vehicle PINs' in the vehicles-tab with the correct service area will be fetched. Read more about uploading PINs for individual vehicles [[Vehicles#Right%20click%20context%20menu|here]] and for multiple vehicles [[Vehicles#Upload Vehicle pins|here]].

Requires WCU version 2.89.0 or higher.

== Signal reader assignments support DREC with IDC assignments ==
In signal reader DREC it was previously only possible to upload sequence files. Now you also can select an existing IDC assignment. Read more about DREC [[Signal Reader Assignment Editor#Recorder - DREC|here]].

== Assignment editor now with permissions for edit and remove assignments ==
You can now set permissions for assignments, controlling who can edit or remove them. Admins and owners of the assignment can designate assignments as private or public, and assign edit permissions to specific users. Non-editors can view but not modify assignments. Read more about it [[Assignment Editor#Assignment permissions|here]].

== Support for UDS service 38 for task type DLT ==
It is now possible to get ECU logs using service 38 in addition to using the DLT daemon for DLT tasks. Read more about it [[Creating a Task#Diagnostic Log and Trace (DLT)|here]].

== Support to copy resource group ==
It is now possible to copy a resource group.

Assignment Editor

2024-12-16T15:55:57Z

Jonathan.olsson: /* Assignment permissions */

[[File:Assignment editor v2.png|none|thumb|944x944px|Assignment Editor start view]]
This panel is for managing assignments. In this version it is signal reader, Area5 and IDC assignments that are possible to handle. Here you can view, edit and copy saved assignments and create a new one. This window will initially not show any assignment and you need to search or click on “Refresh”. If you are only interested in one type of assignment you can select the specific type at the “Type” column. Which columns that are visible can be managed with the views button in the bottom right of the table. Read more about views [[Save View and Search Expressions|here]]. When selecting an assignment in the table the right panel will show a summary of the assignment.

Read more about specific assignment:

* [[Area5 Assignment Editor|Area5 Assignment]]
*[[Signal Reader Assignment Editor|Signal Reader Assignment]]
*[[IDC Assignment Editor|IDC Assignment]]

==Create a new assignment==
To create a new assignment, click on the “new” button. Then a new Tab shows up where you select the necessary things to create a new assignment.
[[File:NewAssignment.png|none|thumb]]

*Left panel you select type of assignment and which A2L files to use (This option will only be possible if the vehicle profile has any A2L files).
*Center panel you sort and select the vehicle profile to use.
*Right panel will show a summary of how the assignment will be. Please note that this will first be visible when a vehicle profile is selected.

To create the assignment click on "Create assignment".

== Manage saved assignments==

===Edit assignment===
Select an assignment in the listgrid. Then click Edit and a new tab with the assignment will appear. Manage the assignment after click save if you want to save the changes.

===Copy assignment===
Select an assignment in the listgrid. Then click Copy and a new tab like creating assignment will appear. Manage the copy assignment like creating a new one except you have to choose a new name for the assignment.

===Delete assignment ===
Select an assignment in the listgrid. Then click Remove and the assignment will be removed.

=== Import/Export assignment ===
Possible to export and import assignments between different portals. This is only available for signal reader assignments.

* Export: Select an assignment and click on export
* Import: Click on import. Add the .zip file and select a vehicle profile

Read more about signal reader import/export [[Signal Reader Assignment Editor#Import/Export assignment|here.]]

== Assignment running in task==
Assignments that are running on a WCU already are also possible to see. Do the following:

# Go to the Task panel.
# Select a task of the type Area5, IDC or Signal Reader.
# Click View Task and then click on view in assignment editor.

== Assignment review ==
In the lower right part of the assignment editor start view, there is support to require other users to do a review of an assignment in order to improve the quality of the created assignments. Read more about that process [[Review assignment process|here]].

== Assignment permissions ==
You can set permissions for assignments to control who can edit or remove them. In the “Public/Private” column, you'll see whether the assignment is public or private, and in the “Can Edit” column, you’ll see if the logged-in user has permission to edit the assignment. Only the admin or the owner of the assignment can manage permissions.

If you don’t have permission to edit an assignment, you can still click "Edit" to view the assignment, but you won’t be able to make changes or save it.

=== To Set Permissions: ===

# Search for and select an assignment.
# Click on "Permissions" at the bottom of the page.
# Select Private in the checkbox to make the assignment private. (Unselect the checkbox to make it public again).
# Add users by clicking on “Add” at the bottom of the list. Users listed in the “Can Edit” section will be able to edit the assignment.
# Click Save to apply the changes and set the permissions.

Assignment Editor

2024-12-16T15:34:09Z

Jonathan.olsson: /* Assignment review */

File:Assignment editor v2.png

2024-12-16T15:32:32Z

Jonathan.olsson:

assignment editor v2

New features in v2.92

2024-12-13T10:17:18Z

Jonathan.olsson: /* Signal reader assignments support DREC with IDC assignments */

== Support for WiFi on platform HMX/V2 ==
In version 2.92, we have added support for WiFi on the HMX/V2 platform in the WCU configuration panel. To access the WiFi settings, the WCU must be running at least version 2.92.0.

== Support for ICCID in the WCU history panel ==
ICCID is now available in the WCU history panel, enabling users to see which SIM card is installed in the WCU. Read more about it [https://wiki.alkit.se/wice292/index.php/Vehicles#Right_click_context_menu here].

== Time Limited Remote Logon ==
It is now possible to specify a time limit (in hours) for the remote logon configuration. If specified, the remote logon configuration will be automatically disabled after the limit has expired.

Depending on the portal setup, the following modes are possible:

* None - not possible to specify a time limit.
* Optional - the user may specify a time limit.
* Required - the user must specify a time limit.

== Fetch uploaded Vehicle PINs ==
It is now possible to fetch PINs for HIA, HIB and Diagnostic firewall disable in the IO-tab of the WCU configuration panel. This is done by setting the checkbox 'Fetch Uploaded PINs' which will fetch and apply any available PINs once you save the configuration. For individual WCUs it is also possible to use the 'Get PINs' button to immediately apply the PINs and receive some additional feedback. Resource groups can only fetch PINs via the checkbox. The PINs will be automatically applied to the corresponding fields if available.

Only PINs that have been uploaded via 'Upload Vehicle PINs' in the vehicles-tab with the correct service area will be fetched.

Requires WCU version 2.89.0 or higher.

== Signal reader assignments support DREC with IDC assignments ==
In signal reader DREC it was previously only possible to upload sequence files. Now you also can select an existing IDC assignment. Read more about DREC [[Signal Reader Assignment Editor#Recorder - DREC|here]].

== Assignment editor now with permissions for edit and remove assignments ==

== Support for UDS service 38 for task type DLT ==
It is now possible to get ECU logs using service 38 in addition to using the DLT daemon for DLT tasks. Read more about it [[Creating a Task#Diagnostic Log and Trace (DLT)|here]].

Signal Reader Assignment Editor

2024-12-12T12:51:45Z

Jonathan.olsson: /* Recorder - DREC */

The Signal Reader Assignment Editor can be found under the tab '''Assignment''' and allows the user to create new assignments for signal reader directly in the portal. This page will guide you through the basics of using the editor.

==Edit/Create a signal reader assignment==

The first tab that you are presented with is the '''Assignment global settings''' tab where you can add information about the assignment so that you can easily keep track of what this assignment is about. Creator and creation date are both automatically filled in and cannot be changed because of consistency.

Under the '''Measurements''' tab, see Figure "Measurement Setups", you are presented to a table of Measurement Setups and an information window. These measurement setups are the core of a signal reader assignment. They contain '''Triggers''' that activate and deactivate on certain conditions provided by the user. Each trigger can contain a '''Recorder''' that contains a list of certain signals that will be measured when the start condition for the respective trigger is met. A trigger can also be used to act as a '''setup switch'''.[[File:Measurement setup.png|none|thumb|608x608px|Measurement Setups]]
When you feel finished with the assignment you can simply click the '''Save assignment''' button in the lower right corner to save the assignment in its current state.
===Trigger===
To add a trigger to a measurement setup, click the '''plus''' button for the respective measurement setup. This will create a new Trigger in the trigger table in the respective measurement setup and the information window will be filled with new settings for this trigger for you to add. In the window, trigger type can be set to different types: Recorder, Setup switch, Pause diagnostics, Start/stop CCP DAQ, Start/stop XCP DAQ and Upload. With Setup switch you will jump/end/restart when the start condition is met.

Fill out the '''start trigger''' '''condition''' for the trigger. This is easiest to do in the '''Edit expression''' window that you can get to by clicking one of the '''Edit''' buttons. To find a new signal to add a condition for, use the '''Add signal''' button. Here, you can browse all signals available for this assignment. Use the dropdown to browse signals from different can-busses and Wice internal signals. If you want to browse the signals currently in use in the assignment for the selected signal source, check the '''Search in assignment''' box. If you want more information about a signal, select it and click '''More info'''. When you have found the signal you want, double click it or select it and click '''Add signal'''. Now you can use the '''Operators''' list to add a condition for the signal, for example " > 0". When you are satisfied with the start condition, you will notice that the Validate button has a yellow warning symbol on it. This means that the expression is unvalidated, press the button to validate the expression. The buttons icon now either turns red (expression is unvalid) or green (expression is correct). See Figure "Validate Button States" for the different state of the validate button. Click Save to save the expression. The list of operators supported in trigger condition is available [[Signal Reader Trigger Expressions|here]].[[File:ValidateButtonStates.png|thumb|Validate Button States|link=https://wiki.alkit.se/wice264/index.php/File:ValidateButtonStates.png|none]]A '''stop trigger condition''' is not required, but can be supplied to determine when the recording should stop. If the stop condition is not supplied, the settings for the recorder will tell when the recording should stop.
===Recorder===
There a two types of recorder, SREC (Signal recorder) and DREC (Diagnostics recorder). Choose which one you want with the radio button at the top of the Recorder tab.
====Recorder - DREC====
DREC (Diagnostics recorder) is used to send diagnostic requests onto the vehicle's communication buses and record the responses. The diagnostic requests are supplied in a sequence file uploaded by the user. The sequence file contains one diagnostic request per line, with the ECU id at the beginning of the line. There can optionally be other information as well. The syntax is the same as the one used for the IDC module, see [[IDC Sequence File Syntax|Sequence File Syntax]]. The result from a DREC will be a diagnostic log file, a text file containing both the requests from the sequence file and the corresponding responses.

The DREC (Diagnostics Recorder) is a tool used to send diagnostic requests onto the vehicle's communication buses and record the responses. The diagnostic requests can be provided in one of two ways:

# By uploading a sequence file, where:
#* The sequence file contains one diagnostic request per line, with the ECU ID at the beginning of the line. Optionally, additional information may also be included. The syntax used for the sequence file is identical to that of the IDC module; for more details, refer to Sequence File Syntax.
# By selecting an existing IDC assignment.

The output generated by DREC is a diagnostic log file, which is a text file containing both the requests (from the sequence file or IDC assignment) and their corresponding responses.

====Recorder - SREC====
SREC (Signal recorder) is used to record signals on the vehicle's communication buses. The result of an SREC is an MDF file containing the time series data of the selected signals.

For signal recorder there is 3 tabs:

* Symbols - Add/Remove/view signals to record
* Frames - Handle frame recorder on Passive CAN and Flexray busses.
* Properties - Settings for the recorder.

===== Symbols: =====
Buttons on the bottom strip:

* Add Signal: Will open a window where signals can be added from. By selecting a signal source the list will be populated with signals available from that source.
* Remove selected: Selected signals will be removed. This is also possible by right click on the list.
* Edit Selected: To edit PLA-compressions (Read more [[PLA-compression window|here]].) and skip factor. Skip factor will be applied to all selected signals.
* More info: Shows more info about passive and Flexrays signals.
* Upload text file with signals names. If the signal does not have a module name it is expected to belong to the already selected signal source/module.
* Paste signals name to be added. If the signal does not have a module name it is expected to belong to the already selected signal source/module.
* Copy signals. In the new window it is possible to switch if it is only the filtered or all signals copied.
[[File:Srec.png|none|thumb|955x955px]]

====== Add Signals: ======
Click on the '''Add Signal''' button to show the window. Select modules/signal source and search up the signals that you want to add. Select those signals and click on "Add signals".
=====Recorder - Properties=====
Under the recorder tab '''Properties''' you can select the properties for the recorder, see Figure "Recorder Properties".

'''Number of shots''' is an important factor for a recorder. A '''shot''' is the term used for a single recording and number of shots is therefore the number of times we should record. A shot is only started when the start trigger condition is met and will continue until any of these events occur:
*The recording fulfills the maximum duration.
*The recording fulfills the minimum duration and the '''stop trigger condition''' is met.
*The recording fulfills the minimum duration and a trigger start a '''setup switch'''.
*The recording fulfills the minimum duration and another recorder starts a '''setup switch'''.
*A setup switch is started manually.
*The assignment is stopped manually.
The '''recorder Setup switch''' is started when recorder has performed its number of shots and all other started recorders have at least fulfilled their minimum duration. It is, like the trigger setup switch, used to switch to/run a measurement setup.

You can also select the '''Pre trigg duration''' which determines the amount of data that will be saved in the flash before the start trigger condition is met. Range is 0 to 2147483647 (231 -1).

The '''Post trigg duration''' is much like the pre trigg duration and determines the amount of data that will be saved after the stop trigger condition is met. Range is 0 to 2147483647 (231 -1).

The '''Minimum duration''' determines the minimum amount of data that needs to be recorded before it becomes possible to cancel the recording through either a stop trigger or a setup swtich started by a trigger or another recorder.

The '''Maximum duration''' determines, as the name suggest, the maximum amount of data that should be recorded. Range is 0 to 2147483647 (231 -1).

The '''Unit''' for the four aforementioned durations can be set to seconds, samples or bytes. If you choose to set them to seconds, the device will use the timestamps of the incoming data to determine the four aforementioned durations.[[File:Recorder properties.png|thumb|600x600px|Recorder Properties|none|link=https://wiki.alkit.se/wice264/index.php/File:Recorder_properties.png]]

== Active signals ==
An Active Signal is a signal that is created by polling an ECU for a numerical value at a predefined frequency. The polling is typically done using the ReadDataByIdentifier diagnostic service. To create an assignment with active signals, the vehicle profile has to have a diagnostic description. This is set in the vehicle profile settings [[Vehicle Pofiles|here]]. There has to be a diagnostic description connected to the vehicle profile when the assignments are created to be able to select active signals. If a vehicle profile is updated, an assignment can be upgraded to match the new vehicle profile by doing a copy. This will automatically upgrade it and if there is a diagnostic description connected it will be possible to use active signals.

Select “Active signal” in signal Source. Then it is possible to select ECU in ECU name. After that available signals will show up and select/deselect works like for the other signal sources.

When creating a task with an assignment that has active signals selected, a button “ECU SW mappings” will show up. If there is a red exclamation mark, a specific software version has to be selected for one or more ECUs. If a recorder signal does not exist in the selected software version it will be removed. Note that the software version has to contain all active signals that exist in the trigger conditions otherwise it will not be possible to create the task.
==Using a portal assignment for a signal reader task==
In order to use a portal assignment. Select the WCUs in the Vehicle tab that you want to create the new signal reader assignment for and click new task. Navigate to the Signal reader tab and click the '''Browse saved assignments''' button and select the assignment you want to use and click '''Ok'''. This assignment will now be used to create the .haf file required by the WCUs to perform the signal reader task. If selecting "Legacy WICE internal signal names" certain wice internal signals names will be translated.
[[File:BrowseSR.png|none|thumb|600x600px|View Assignments]]
Legacy WICE internal signal names:
{| class="wikitable"
! From
!To
|-
|WICE.Longitude
|WICE_Generic_Internal.Longitude_0020
|-
|WICE.Latitude
|WICE_Generic_Internal.Latitude_0020
|-
| WICE.CSQ
| WICE_Generic_Internal.CSQ_0020
|-
|WICE.WCU_Voltage
|WICE_Generic_Internal.WCU_Voltage_0103
|-
|WICE.WCU_Temp
|WICE_Generic_Internal.WCU_Temp_0104
|-
|WICE.Time_Since_Epoch
|WICE_Generic_Internal.Time_Since_Epoch_0090
|-
|WICE.Start_Signal
|WICE_Generic_Internal.Start_Signal_0100
|}
== Select different communication interface or transport protocol ==
Under the "Modules" tab, the different signal sources are visible. In the "I/O" column, the selected communication interface and transport protocol are shown. By selecting a row and then clicking on the button “Edit Interface” this can be changed. Currently this is only possible for modules with type “A2L” or "Diagnostics." When changing this, a validation of the settings with what is red from the corresponding A2L file is done. If the validation is successful, a green icon will appear. If the icon is a red cross the A2L file does not contain the necessary information for the setting.

When selecting between CAN and Ethernet/DoIP diagnostics, a window pops up where you can select the interface between "Default Channel", "CAN" or "DoIP". Selecting "Default Channel" means that the default channel in the signal reader module settings on the wcu is going to be used. Interface "CAN" a specific CAN interface can be selected to be used for the diagnostic requests. If selecting "DoIP", the diagnostics will be performed over Ethernet using the Diagnostics-over-IP (DoIP) protocol. In this case, you can also select whether to use the IP address broadcasted by the vehicle in a "Vehicle Announcement" message, or you can specify the IP address explicitly (in which case the Vehicle Announcement will be ignored). The DoIP port number to use (default 13400) can also be specified.

A2L modules support the following interfaces, CPP-CAN, XCP-CAN, XCP-TCP, XCP-UDP and UDS (2C/2A).[[File:DoIP-ass-ed.png|alt=CAN or DoIP settings|thumb|CAN or DoIP settings|none]]

== Record frames with filter ==
Frame recorder can be used on FlexRay and CAN-bus. In a signal recorder the frame recorder with or without filter can be activated.

To activate/deactivate the frame recorder for a module either click on the active icon or select a specific row and click Toggle.

To edit the filter either double click on row or click on edit filter.
[[File:Framerecorder.png|none|thumb|482x482px]]

== User defined signals ==
In this tab are user defined signals handled.

* Add and remove signals by clicking the respective button.
* Signals names are set on creation and can not be changed after that.
* Calculation formula is the formula that will be calculated for the signal's value. For example writing “module.signal_name + 10” will increase “signal_name” by 10.
* Update on signals is determining when the formula shall be calculated. Each time that signals get present the new user defined signal will be calculated.

This type of signals can then be used in triggers and recorder by finding the name that will be “UD.<Name>”.
[[File:UD Editor2.png|none|thumb|483x483px]]

== Import/Export assignment ==
Signal reader assignment can be exported and then be imported in another portal. Versions can mismatch with one version and still work. If it differs more, use it carefully. When importing an assignment and vehicle profile needs to be selected. This profile should be similar to that one the original assignment was based on. If some signals or signals source do not exist in the new profile that was used in assignment a warning message will be shown with information about what is missing. If missing signals were used in a trigger expression the state will be set as invalid. Today there is no way to export and import a vehicle profile. So these have to be done manually.

== DAQ/Event-list ==
If the assignment contains signals source that are compatible with DAQ list or Event channels a tab with name “DAQ/Event” will be visible. After signals have been added to the recorder it can be added to the DAQ list.

=== Add new DAQ-List ===
To add a new DAQ list click on green plus icon on specific Measurement setup and ECU name. The new window shows all the DAQ-list that was predefined in the a2l-file. '''NOTE! What information that will be shown depends on what transport protocol that is selected in the module settings.''' If there is no information the table will be empty. Choose either one from the list or select “New blank” to define DAQ-list yourself.
[[File:AddNewDAQ.png|none|thumb|528x528px]]

=== Manage DAQ-List ===
On “Edit DAQ” following settings can be made:

* Name
* DAQ number: Must be unique
* Periodicity: Will not affect the real periodicity is only for information.
* Max bytes/Max Frame: Depending on measurement is over can or ethernet.
* Prescaler

[[File:DAQList.png|none|thumb|542x542px]]

=== Manage Event channel ===
Manage event channels is similar to DAQ-list. In DAQ list you add signals but in event channels you add DAQ-list. With “Edit event” following settings can be made:

* Name
* Channel number: Must be unique.
* Periodicity: Will not affect the real periodicity is only for information.
* Max DAQs: Note that 255 meaning infinity.
* Max Size of DAQs: Max byte each DAQ list can contain.
* Priority

New features in v2.92

2024-12-12T12:03:24Z

Jonathan.olsson:

Vehicle Profiles

2024-10-11T12:57:17Z

Jonathan.olsson: /* Define CAN interfaces */

[[File:Vehicle-profiles-generate-template.png|alt=Vehicle Profiles Panel|none|thumb|1000x1000px|Vehicle Profiles Panel]]
As an administrator, it is possible to define vehicle profiles from version 2.45 of the WICE portal. The vehicle profiles panel is located in the [[The Portal Administrator View#The Administration Tab|the administration tab]] as can be seen in Figure "Vehicle Profiles Panel".

== Add a new vehicle profile ==
To add a new vehicle profile, click "Add new Vehicle Profile" in the "Vehicle Profiles" portlet to the left in the view. Choose a name and press enter. This will create a new vehicle profile with no interfaces defined.

=== Define CAN interfaces ===
[[File:Custom car types 2.png|thumb|300x300px|Add CAN Dialog]]
To define a new CAN interface for a vehicle profile, select the vehicle profile in the "Vehicle Profiles" portlet and then click "Add CAN" in the CAN portlet. This will open up the dialog as can be seen in Figure "Add CAN Dialog".

The majority of the interface attributes should be self explanatory but the DBC file may need some clarification.

Depending on the portal settings settings, J1939 and CAN decoding can be activated. J1939 is either true or false but CAN decoding has a version. Today all CAN with decoding has to use the same version.

==== Select DBC file ====
A CAN bus needs to be associated with a DBC file and when defining a CAN interface one have the option to select an already upload DBC file or upload a new one. Uploading DBC files can be done via the DBC files portlet (described in [[#Manage DBC files]]) or directly in the select DBC files grid shown in Figure "Select DBC Files Grid".

=== Define ECU interfaces ===
ECU interfaces are connected to a CAN interface. When adding a new ECU you will first be prompted to choose ECU name. The ECU names presented here are those ECU names that have a A2L file associated with them. When a ECU name is chosen, the available A2L files for that ECU are displayed and can be chosen. Drag and drop is supported when choosing files. You may choose multiple files per ECU.
It is possible to add a seed/key to ECUs individually. The value of each Seed/Key is never displayed for the user as it can be considered confidential.
[[File:AddNewECU.png|none|thumb|363x363px|Add new ECU]]

=== Define Flexray interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define ETH interfaces ===
The interfaces are similar to the CAN interfaces.

=== Define LIN interfaces ===
The interfaces are similiar to the CAN interfaces.[[File:Custom car types 3.png|thumb|300x300px|Select DBC Files Grid|none]]

== Copy / Create new vehicle profile from an existing one ==
It is possible to create a new vehicle profile based on an existing one by selecting the vehicle profile you want to create the new vehicle profile from and then clicking '''Copy'''. You will now get a new vehicle profile named "Original name - Copy"

== Diagnostic templates - Manage active signals connected to the vehicle profile ==
[[File:Vehicle-profile-red-marked-diagnostic-template.png|alt=The "Diagnostic templates" button|left|thumb|The "Diagnostic templates" button]]
[[File:Edit-diag-ref-edit-mode.png|thumb|Diagnostic templates dialog - Edit mode|379x379px]]
[[File:Edit-diag-ref-view-mode.png|center|thumb|Diagnostic templates dialog - Choose mode|230x230px]]

Decide which ECUs shall be connected to the vehicle profile for when measuring [[Signal Reader Assignment Editor#Active signals|active signals]] (diagnostics). Either by adding ECUs manually or by picking from uploaded description files (see [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] for how to upload).

Multiple files and/or single picking of ECUs is possible. The choice is then saved as a Diagnostic template and can be reused by other vehicle profiles.

How to create/edit a Diagnostic template:

# Upload description files in [[Vehicle_Profiles#Manage_Description_files|The Description Files portlet]] to make files and ECUs available.
# In the “Vehicle Profiles” tab - in the “Vehicle Profile”-section - find the vehicle profile you want to connect a description file to and select it or do not select any if only editing/viewing Diagnostic templates is desired.
# Click on “Diagnostic template”.
# Choose an already made template, create a new or edit an existing.
## When in create-/edit-mode - move ECUs/files from left to right to select them and vice versa.
## Save any changes that was made.
# If a vehicle profile was selected in step 2: Click "Choose diagnostic template" to associate a template with the selected vehicle profile.

=== Generate a Diagnostic Template ===
[[File:Vehicle-profile-red-marked-generate-diagnostic-template.png|alt=The "Generate diagnostic template" button|thumb|The "Generate diagnostic template" button]]
Based on having vehicles reporting the ECUs software version, using an SoH task, there is opportunity to let the system create a template based on what is reported. When pressing the button 'Generate diagnostic template', you will presented with the following window:
[[File:Vehicle-profiles-generate-template-result1.png|alt=A generated diagnostic template|left|thumb|A generated diagnostic template]]
There are three sections:

* Non Existing, no diagnostic data for the specific ECU software version exists. Upload a suitable SDDB file to fix this.
* Existing, those have been selected
* Clashes. It might be the case that there exists multiple ECUs with the same address but with different names having the same software version. You must select which to use.

When you are done you simply press update or check 'Add new template' to create an entirely new template.

== Manage Description files ==
[[File:Vehicle-description-files.png|thumb|The Vehicle Description files portlet]]

The "Vehicle Description files" portlet let the user upload, change or remove description files. These files are used to describe the vehicle. Supported description files are:

* '''DBC''' - describing CAN interfaces
* '''FIBEX''' - describing Flexray interfaces
* '''A2L''' - describing ECU interfaces
* '''ECU''' '''Diagnostics''' (e.g. sddb-files) - provides which ECUs that are available for creating [[Vehicle_Profiles#Diagnostic_templates_-_Manage_active_signals_connected_to_the_vehicle_profile|diagnostic templates]].
*'''LDF''' - describing LIN interfaces

=== Upload new Description file ===
To upload a new Description file, click the "Upload new file" button and choose the file to upload.

===== Upload A2L file =====
When uploading an A2L file there is the possibility to specify file version. This can be used to validate if a created Signal Reader and Area5 assignment can run on a given WCU.

There is also the possibility to specify which ECU name that the A2L file. This must be specified and cannot be edited later so make sure you choose the correct ECU. The list you are presented with when choosing ECU name

are the ECU names that have been found in uploaded ECU diagnostic files.
[[File:UploadNewA2lFile.png|none|thumb|Upload new A2L file]]

=== Edit Description file ===
To edit an uploaded Description file, select the Description file and click "Edit selected". A new window will pop up which let you do the following:

==== Replace Description file: ====
Replace the current Description file with another file.

==== Change name: ====
Change the name that references the Description file in the Description file.

==== Comment: ====
Add a comment to the Description file.

==== Enable/disable: ====
Enable/disable the Description file.

New features in v2.91

2024-10-11T08:46:46Z

Jonathan.olsson: /* Visualize the measured signals */

== Visualize the validation reasons for each WCU within a resource group ==
The user can now view all validations for each WCU within a resource group while creating a new task. This can be accessed by clicking the new 'Show Resources' button or by double-clicking the corresponding row. Read more about it [https://wiki.alkit.se/wice291/index.php/New_task here].

== Implemented new permission for inactive vehicles/WCUs ==
Introduced new permissions for a user to toggle the visibility of inactive vehicles/WCUs. The vehicle permission is referred to as 'View Inactive Vehicle Permission,' while the WCU permission is called 'View Inactive WCU Permission.'

== Edit test request name on add vehicle (Not in all versions of the Portal) ==
The "Edit Test Request Name" feature was previously available exclusively within the "Edit Vehicle" section of the application. Now, the feature has been expanded to also be available in the "Add Vehicle" section. This means that users can set or edit the test request name right when they are adding a new vehicle to the system, instead of waiting until later when editing the vehicle.

== Copy data from tables and possible to mark text ==
In some tables it is now possible to select text from rows. Many tables within the application now include a "Copy" button, which functions like an export tool. When this button is clicked, a new window appears, allowing users to select which columns they want to export. And in some cases it is possible to only select rows that have been filtered.

== Visualize the measured signals ==
For the Signal Reader task, a new feature has been added that displays which signals were successfully measured and which ones were not for a specific recorded file. To access this feature, follow these steps: select a Signal Reader task, click on 'Get Result Files,' choose an MDF file, and then click on 'Measured Signals. Read more [[Measured signals|here]].

== WMU information tab (Not in all versions of the Portal) ==
If the portal supports [[WMU]] a tab is shown that lists all known wmus. Read more [[WMU information tab|here]].

== sw_changed will only be set on a2l-module if the assignment has any signal selected ==
sw_changed for signal reader will only be set on a2l-module if the module has signals that are in use. Read more about sw_changed [[Reasons behind SW changed|here.]]

Measured signals

2024-10-11T08:39:12Z

Jonathan.olsson: Created page with "In result files for a signal reader task on a mdf file it is possible to show which signals that were measured. To open, select a file of type mdf. On the top right button bar click on “Measured signals”. If the signal reader task is created with an assignment from portals assignment editor it will show which signals that were not measured. A measured file (mdf) is recorder specific and therefore to show signals that were not measured the correct recorder from assi..."

In result files for a signal reader task on a mdf file it is possible to show which signals that were measured. To open, select a file of type mdf. On the top right button bar click on “Measured signals”. If the signal reader task is created with an assignment from portals assignment editor it will show which signals that were not measured.

A measured file (mdf) is recorder specific and therefore to show signals that were not measured the correct recorder from assignment has to be selected. The portal will try to match which recorder that was used.
[[File:Measured signals.png|none|thumb|1094x1094px]]

File:Measured signals.png

2024-10-11T08:38:51Z

Jonathan.olsson:

measured signals

New features in v2.91

2024-10-11T08:01:47Z

Jonathan.olsson: /* WMU information tab (Not in all versions of the Portal) */

== Visualize the validation reasons for each WCU within a resource group ==
The user can now view all validations for each WCU within a resource group while creating a new task. This can be accessed by clicking the new 'Show Resources' button or by double-clicking the corresponding row. Read more about it [https://wiki.alkit.se/wice291/index.php/New_task here].

== Implemented new permission for inactive vehicles/WCUs ==
Introduced new permissions for a user to toggle the visibility of inactive vehicles/WCUs. The vehicle permission is referred to as 'View Inactive Vehicle Permission,' while the WCU permission is called 'View Inactive WCU Permission.'

== Edit test request name on add vehicle (Not in all versions of the Portal) ==
The "Edit Test Request Name" feature was previously available exclusively within the "Edit Vehicle" section of the application. Now, the feature has been expanded to also be available in the "Add Vehicle" section. This means that users can set or edit the test request name right when they are adding a new vehicle to the system, instead of waiting until later when editing the vehicle.

== Copy data from tables and possible to mark text ==
In some tables it is now possible to select text from rows. Many tables within the application now include a "Copy" button, which functions like an export tool. When this button is clicked, a new window appears, allowing users to select which columns they want to export. And in some cases it is possible to only select rows that have been filtered.

== Visualize the measured signals ==

== WMU information tab (Not in all versions of the Portal) ==
If the portal supports [[WMU]] a tab is shown that lists all known wmus. Read more [[WMU information tab|here]].

== sw_changed will only be set on a2l-module if the assignment has any signal selected ==
sw_changed for signal reader will only be set on a2l-module if the module has signals that are in use. Read more about sw_changed [[Reasons behind SW changed|here.]]

WMU information tab

2024-10-11T08:01:11Z

Jonathan.olsson: wmu informaiton tab

If the portal supports [[WMU]] a tab is shown that lists all known wmus.

* If a WMU has been reported but not configured the configured column will be red and reported on will have a date when it last talked.
* If a WMU has been configured but never talked to the portal configured will be green and reported on will show “never”.
* If a WMU has been configured and is talking to the portal configured will be green and reported on show a date. This is the correct state of a potential working WMU.

[[File:WMU Information tab.png|none|thumb|965x965px]]

File:WMU Information tab.png

2024-10-11T07:56:11Z

Jonathan.olsson:

WMU Information tab

New features in v2.91

2024-10-11T07:53:45Z

Jonathan.olsson: /* sw_changed will only be set on a2l-module if the assignment has any signal selected */

== Visualize the validation reasons for each WCU within a resource group ==
The user can now view all validations for each WCU within a resource group while creating a new task. This can be accessed by clicking the new 'Show Resources' button or by double-clicking the corresponding row. Read more about it [https://wiki.alkit.se/wice291/index.php/New_task here].

== Implemented new permission for inactive vehicles/WCUs ==
Introduced new permissions for a user to toggle the visibility of inactive vehicles/WCUs. The vehicle permission is referred to as 'View Inactive Vehicle Permission,' while the WCU permission is called 'View Inactive WCU Permission.'

== Edit test request name on add vehicle (Not in all versions of the Portal) ==
The "Edit Test Request Name" feature was previously available exclusively within the "Edit Vehicle" section of the application. Now, the feature has been expanded to also be available in the "Add Vehicle" section. This means that users can set or edit the test request name right when they are adding a new vehicle to the system, instead of waiting until later when editing the vehicle.

== Copy data from tables and possible to mark text ==
In some tables it is now possible to select text from rows. Many tables within the application now include a "Copy" button, which functions like an export tool. When this button is clicked, a new window appears, allowing users to select which columns they want to export. And in some cases it is possible to only select rows that have been filtered.

== Visualize the measured signals ==

== WMU information tab (Not in all versions of the Portal) ==

== sw_changed will only be set on a2l-module if the assignment has any signal selected ==
sw_changed for signal reader will only be set on a2l-module if the module has signals that are in use. Read more about sw_changed [[Reasons behind SW changed|here.]]

New features in v2.91

2024-10-11T07:46:41Z

Jonathan.olsson: /* Copy data from tables and possible to mark text */

== Visualize the validation reasons for each WCU within a resource group ==
The user can now view all validations for each WCU within a resource group while creating a new task. This can be accessed by clicking the new 'Show Resources' button or by double-clicking the corresponding row. Read more about it [https://wiki.alkit.se/wice291/index.php/New_task here].

== Implemented new permission for inactive vehicles/WCUs ==
Introduced new permissions for a user to toggle the visibility of inactive vehicles/WCUs. The vehicle permission is referred to as 'View Inactive Vehicle Permission,' while the WCU permission is called 'View Inactive WCU Permission.'

== Edit test request name on add vehicle (Not in all versions of the Portal) ==
The "Edit Test Request Name" feature was previously available exclusively within the "Edit Vehicle" section of the application. Now, the feature has been expanded to also be available in the "Add Vehicle" section. This means that users can set or edit the test request name right when they are adding a new vehicle to the system, instead of waiting until later when editing the vehicle.

== Copy data from tables and possible to mark text ==
In some tables it is now possible to select text from rows. Many tables within the application now include a "Copy" button, which functions like an export tool. When this button is clicked, a new window appears, allowing users to select which columns they want to export. And in some cases it is possible to only select rows that have been filtered.

== Visualize the measured signals ==

== WMU information tab (Not in all versions of the Portal) ==

== sw_changed will only be set on a2l-module if the assignment has any signal selected ==