WCU platform - Revision history

Mathias: /* WCU Hardware Platform */

2025-04-25T07:56:23Z

WCU Hardware Platform

← Older revision		Revision as of 07:56, 25 April 2025
Line 6:		Line 6:
	The following hardware platforms are supported for the WICE WCU:		The following hardware platforms are supported for the WICE WCU:

	* Host Mobility MX-4 (T20, T30, T30FR and V61)		* Host Mobility MX-4 (T20, T30, T30FR and V61)
	* ~~Fältcom MIIPS Committo~~		* SETEK HMX
	* Raspberry Pi		* Raspberry Pi
	* Nvidia Jetson Xavier		* Nvidia Jetson Xavier

Mathias: /* DLT module */

2025-03-06T11:34:51Z

DLT module

← Older revision		Revision as of 11:34, 6 March 2025
Line 101:		Line 101:

	==== DLT module ====		==== DLT module ====
	The DLT module supports read-out of Diagnostic Log Trace files. See [[DLT Module\|DLT module]].		The DLT module supports read-out of Diagnostic Log Trace files. The read-out can be done either using an in-vehicle DLT daemon, or using UDS Service 38 file transfer. See [[DLT Module\|DLT module]].

	==== DoIP module ====		==== DoIP module ====

Mathias at 11:33, 6 March 2025

2025-03-06T11:33:56Z

← Older revision		Revision as of 11:33, 6 March 2025
Line 12:		Line 12:

	Depending on the specific hardware platform, the WCU supports a number of communication interfaces, such as CAN, LIN, FlexRay and Ethernet and that be configured in different ways using the WICE Portal.		Depending on the specific hardware platform, the WCU supports a number of communication interfaces, such as CAN, LIN, FlexRay and Ethernet and that be configured in different ways using the WICE Portal.

			The WCU has the following communication interfaces (some of which are optional):

			* a point-to-point (ppp) interface using a 2G/3G/4G mobile data modem
			* optionally, a WiFi wireless LAN interface
			* one to four wired ethernet interfaces.
			* two to six Controller Area Network (CAN) interfaces
			* optionally a FlexRay interface
			* optionally, one or more LIN interfaces
			* one to two USB interfaces.

			The unit has the following storage mechanisms:

			* internal flash memory for persistent storage
			* removable SD card for temporary storage

			The unit has the following power modes:

			* running (full functionality available)
			* sleep (suspended state)
			* deep sleep (low-power suspended state)

	The WCU platform can also support some limited user-interaction through light-emitting diodes (LED) on the side of the unit. A description of the LEDs is available [[WCU LEDs\|here]].		The WCU platform can also support some limited user-interaction through light-emitting diodes (LED) on the side of the unit. A description of the LEDs is available [[WCU LEDs\|here]].

Mathias: /* WCU Modules */

2024-09-05T11:53:30Z

WCU Modules

← Older revision		Revision as of 11:53, 5 September 2024
Line 45:		Line 45:
	* DoIP		* DoIP
	* ETAS		* ETAS
			* Ethernet capture
	* File fetcher		* File fetcher
	* Ethernet capture
	* GPS		* GPS
	* IDC		* IDC
Line 52:		Line 52:
	* LPD		* LPD
	* M-Log		* M-Log
			* MQTT
	* Rapid Prototyping		* Rapid Prototyping
	* Signal Reader		* Signal Reader
Line 114:		Line 115:
	==== M-Log module ====		==== M-Log module ====
	The M-log module makes it possible to use an M-Log data logger connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the M-Log and data can be offloaded and uploaded to the portal.		The M-log module makes it possible to use an M-Log data logger connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the M-Log and data can be offloaded and uploaded to the portal.

			==== MQTT module ====
			The MQTT module makes it possible to collect data from another system using an MQTT broker and specifying MQTT topics.

	==== Rapid Prototyping module ====		==== Rapid Prototyping module ====

Mathias: /* WCU Modules */

2022-12-22T14:51:38Z

WCU Modules

← Older revision		Revision as of 14:51, 22 December 2022
Line 45:		Line 45:
	* DoIP		* DoIP
	* ETAS		* ETAS
			* File fetcher
	* Ethernet capture		* Ethernet capture
	* GPS		* GPS
	* IDC		* IDC
			* IPEmotion RT
	* LPD		* LPD
	* M-Log		* M-Log
Line 59:		Line 61:
	==== Arcos module ====		==== Arcos module ====
	The Arcos module makes it possible to use an Arcos data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the Arcos and data can be offloaded and uploaded to the portal.		The Arcos module makes it possible to use an Arcos data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the Arcos and data can be offloaded and uploaded to the portal.

	==== Area5 module ====		==== Area5 module ====
	The Area5 module is used to read out ECU memory segments using CCP or XCP. The binary data of the memory segments are uploaded to the back-end where they are translated into parameter sets and signals.		The Area5 module is used to read out ECU memory segments using CCP or XCP. The binary data of the memory segments are uploaded to the back-end where they are translated into parameter sets and signals.
Line 91:		Line 94:

	==== File Fetcher Module ====		==== File Fetcher Module ====
	The ~~only configuration in the~~ File Fetcher ~~Module is the debug level which specifies the amount~~ of ~~logging~~ from the WCU ~~regarding its handling of the File fetcher task~~.		The File Fetcher module supports uploading of files collected from a unit connected to the WCU.

	==== GPS Module ====		==== GPS Module ====
Line 102:		Line 105:
	IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.		IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.
	An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].		An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].

			==== IPEmotion RT ====
			The IPEmotion RT module makes it possible to use an IPEmotion RT data logger (from Ipetronik) connected to the WCU through an Ethernet port. Measurement tasks can be downloaded to the logger and data can be offloaded and uploaded to the portal.

	==== LPD module ====		==== LPD module ====

Mathias: /* WCU Modules */

2022-12-22T14:47:43Z

WCU Modules

← Older revision		Revision as of 14:47, 22 December 2022
Line 42:		Line 42:
	* Blue piraT		* Blue piraT
	* Canrecorder		* Canrecorder
			* DLT
	* DoIP		* DoIP
	* ETAS		* ETAS
Line 75:		Line 76:

	==== DLT module ====		==== DLT module ====
	See [[DLT Module\|DLT module]].		The DLT module supports read-out of Diagnostic Log Trace files. See [[DLT Module\|DLT module]].

	==== DoIP module ====		==== DoIP module ====

Mathias: /* WCU Modules */

2022-12-22T14:46:14Z

WCU Modules

← Older revision		Revision as of 14:46, 22 December 2022
Line 47:		Line 47:
	* GPS		* GPS
	* IDC		* IDC
			* LPD
	* M-Log		* M-Log
	* Rapid Prototyping		* Rapid Prototyping
Line 100:		Line 101:
	IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.		IDC supports diagnostics over CAN using ISO15765-2 and over IP/Ethernet using ISO13400. Both physical and functional ECU addressing is supported.
	An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].		An IDC sequence file can in addition to diagnostic requests also contain commands, as described in [[IDC sequence file commands]].

			==== LPD module ====
			The LPD module supports long term driveline testing using a custom built Android app that connects to the WICE WCU.

	==== M-Log module ====		==== M-Log module ====

Robin.karhu: /* File Fetcher Module */

2022-02-02T11:30:39Z

File Fetcher Module

← Older revision		Revision as of 11:30, 2 February 2022
Line 89:		Line 89:

	==== File Fetcher Module ====		==== File Fetcher Module ====
	The only configuration in the ~~Feile~~ Fetcher Module is the debug level which specifies the amount of logging from the WCU regarding its handling of the File fetcher task.		The only configuration in the File Fetcher Module is the debug level which specifies the amount of logging from the WCU regarding its handling of the File fetcher task.

	==== GPS Module ====		==== GPS Module ====

Loe.Lindstrom: /* CAN Recorder Module */

2022-02-02T11:29:24Z

CAN Recorder Module

← Older revision		Revision as of 11:29, 2 February 2022
Line 72:		Line 72:
	The CAN Recorder Module supports frame logging on the CAN-buses the WCU is connected to. Filters for the ECU identifiers to log can be		The CAN Recorder Module supports frame logging on the CAN-buses the WCU is connected to. Filters for the ECU identifiers to log can be
	defined in the WICE Portal interface when creating a CAN Recorder measurement task.		defined in the WICE Portal interface when creating a CAN Recorder measurement task.

			==== DLT module ====
			See [[DLT Module\|DLT module]].

	==== DoIP module ====		==== DoIP module ====

Loe.Lindstrom: /* WCU Modules */ Added file fetcher

2022-02-02T11:20:53Z

WCU Modules: Added file fetcher

← Older revision		Revision as of 11:20, 2 February 2022
Line 84:		Line 84:
	The ETAS module makes it possible to use an ETAS ES720 measurement system connected to the WCU through an Ethernet port.		The ETAS module makes it possible to use an ETAS ES720 measurement system connected to the WCU through an Ethernet port.
	Measurement tasks can be downloaded to the ES720 and measurement data can be offloaded and uploaded to the WICE Portal.		Measurement tasks can be downloaded to the ES720 and measurement data can be offloaded and uploaded to the WICE Portal.

			==== File Fetcher Module ====
			The only configuration in the Feile Fetcher Module is the debug level which specifies the amount of logging from the WCU regarding its handling of the File fetcher task.

	==== GPS Module ====		==== GPS Module ====