New features in v2.97 - Revision history

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

2026-02-20T08:18:11Z

Support for WCU hardened mode.

← Older revision		Revision as of 08:18, 20 February 2026
Line 7:		Line 7:

	== Support for WCU hardened mode. ==		== 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~~.”		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.		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.

Robin.karhu: /* Vehicle Communication Forwarder now uses SGA */

2026-02-19T17:37:33Z

Vehicle Communication Forwarder now uses SGA

← Older revision		Revision as of 17:37, 19 February 2026
Line 52:		Line 52:

	== Vehicle Communication Forwarder now uses SGA ==		== Vehicle Communication Forwarder now uses SGA ==
	Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab\|via PIE]] or [[Vehicles#Upload Vehicle pins\|from file]].		[[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.		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.
Line 61:		Line 61:
	[[File:MRCOM forwarding mode.png\|thumb\|MRCOM forwarding]]		[[File:MRCOM forwarding mode.png\|thumb\|MRCOM forwarding]]
	[[File:Raw MRCOM.png\|thumb\|Raw MRCOM]]		[[File:Raw MRCOM.png\|thumb\|Raw MRCOM]]
	In addition to standard MRCOM forwarding via SGA, a VCF can now be configured to instead use raw MRCOM via ethernet.		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.		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.		Only available if Vehicle Communication Forwarder is enabled for the portal.

Robin.karhu: /* Vehicle Communication Forwarder now uses SGA */

2026-02-19T17:34:16Z

Vehicle Communication Forwarder now uses SGA

← Older revision		Revision as of 17:34, 19 February 2026
Line 54:		Line 54:
	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]].		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 ~~for SGA on area 0x17~~ 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.		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.		Only available if Vehicle Communication Forwarder is enabled for the portal.

Robin.karhu: /* Vehicle Communication Forwarder now uses SGA */

2026-02-19T17:33:41Z

Vehicle Communication Forwarder now uses SGA

← Older revision		Revision as of 17:33, 19 February 2026
Line 52:		Line 52:

	== Vehicle Communication Forwarder now uses SGA ==		== Vehicle Communication Forwarder now uses SGA ==
	Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and ~~PINs~~ must instead be uploaded [[The Portal Administrator View#The Resource Groups Tab\|via PIE]] or [[Vehicles#Upload Vehicle pins\|from file]].		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 for SGA on area 0x17 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.		In addition to checking if there is a PIN available for SGA on area 0x17 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.

Robin.karhu: /* Raw MRCOM mode for Vehicle Communication Forwarder */

2026-02-19T16:07:47Z

Raw MRCOM mode for Vehicle Communication Forwarder

← Older revision		Revision as of 16:07, 19 February 2026
Line 55:		Line 55:

	In addition to checking if there is a PIN available for SGA on area 0x17 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.		In addition to checking if there is a PIN available for SGA on area 0x17 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 ==		== Raw MRCOM mode for Vehicle Communication Forwarder ==
Line 62:		Line 64:

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

Robin.karhu: VCF SGA and raw MRCOM

2026-02-19T16:04:58Z

VCF SGA and raw MRCOM

← Older revision		Revision as of 16:04, 19 February 2026
Line 50:		Line 50:
	[[File:Check PINs result.png\|thumb\|Check PINs result]]		[[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.		Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU. Likewise, checking PINs for DLT tasks was previously limited to resource groups but will now also work for individual WCUs connected to a vehicle.

			== Vehicle Communication Forwarder now uses SGA ==
			Vehicle Communication Forwarder (VCF), or MRCOM, now requires PINs for SGA instead of HIA and HIB. Previously these PINs could be entered manually, but that is now no longer possible and PINs 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 for SGA on area 0x17 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.

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

Robin.karhu: /* Show whether PINs are available for a vehicle */

2026-02-19T15:30:44Z

Show whether PINs are available for a vehicle

← Older revision		Revision as of 15:30, 19 February 2026
Line 48:		Line 48:
	== Show whether PINs are available for a vehicle ==		== 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.		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.		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.

Robin.karhu: /* Show whether PINs are available for a vehicle */

2026-02-19T15:21:44Z

Show whether PINs are available for a vehicle

← Older revision		Revision as of 15:21, 19 February 2026
Line 49:		Line 49:
	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.		If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle.

	Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU.		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.

Robin.karhu: /* Show whether PINs are available for a vehicle */

2026-02-19T15:19:43Z

Show whether PINs are available for a vehicle

← Older revision		Revision as of 15:19, 19 February 2026
Line 47:		Line 47:

	== Show whether PINs are available for a vehicle ==		== 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.		If enabled for the portal, it will now be possible to check which ECUs and areas have PINs available for a given vehicle. This can be done when editing a vehicle, when editing or creating a new DLT task, or, if Vehicle Communication Forwarder is also enabled in the portal, from the IO tab when editing the WCU configuration of a WCU with a connected vehicle.

			Checking PINs from the IO tab of the WCU configuration was previously limited to only HIA and HIB PINs, but will now show for any available ECU.

Robin.karhu: check PINs

2026-02-19T15:16:41Z

check PINs

← Older revision		Revision as of 15:16, 19 February 2026
Line 45:		Line 45:

	To read more about DLT tasks, [[Creating a Task#Diagnostic Log and Trace (DLT)\|click here]].		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.