Vehicle Communication Forwarder: Difference between revisions

From WICE Wiki v2.97
Jump to navigation Jump to search
No edit summary
No edit summary
 
(8 intermediate revisions by one other user not shown)
Line 1: Line 1:
A Vehicle Communication Forwarder is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a Vehicle Communication Forwarder means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.
A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.


To read more about adding a Vehicle Communication Forwarder, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.
It is also possible to configure LIN channels on the VCF, with the same requirements.
[[File:Vehicle Communications Forwarder CAN channels.png|thumb|CAN channel configuration|769x769px]]
 
Due to now using SGA instead of HIA and HIB, requires WCU version 2.97.0 or higher (previously required 2.89.0).
 
To read more about adding a VCF, see the [[I/O configurations#Add CAN channels|Add CAN channels]] section in I/O configurations.
 
A PIN for SGA area 0x5 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either [[Vehicles#Right click context menu|individual]] or for [[Vehicles#Upload Vehicle pins|multiple]] vehicles. As of 2.94.0 it is also possible to [[The Portal Administrator View#The Resource Groups Tab|fetch PINs from PIE]] for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.
[[File:VCF MRCOM forwarding.png|thumb|768x768px|VCF MRCOM forwarding with CAN and LIN channel configurations]]
[[File:VCF raw MRCOM.png|thumb|769x769px|VCF raw MRCOM with CAN and LIN channel configurations]]

Latest revision as of 14:01, 27 April 2026

A Vehicle Communication Forwarder (VCF) is used as an extension of the measuring capabilities of a WCU when measuring on CAN channels. Configuring a VCF means adding a number of CAN channels. The configurations for these channels differ slightly from the configurations of the WCU's CAN channels. Speed is not configured, instead each channel requires an ECU-ID in the hexadecimal format of either 0x#### or ####, as well as a unique CAN bus number.

It is also possible to configure LIN channels on the VCF, with the same requirements.

Due to now using SGA instead of HIA and HIB, requires WCU version 2.97.0 or higher (previously required 2.89.0).

To read more about adding a VCF, see the Add CAN channels section in I/O configurations.

A PIN for SGA area 0x5 has to be uploaded for the VCF to function correctly. Uploading PINs can be done from file for either individual or for multiple vehicles. As of 2.94.0 it is also possible to fetch PINs from PIE for the resources in a group. Once the PINs have either been uploaded from file or fetched from PIE they will then be applied automatically to the VCF via the WCU.

VCF MRCOM forwarding with CAN and LIN channel configurations
VCF raw MRCOM with CAN and LIN channel configurations