X2E: Xoraya¶

Vendor information

Vendor	Web page	Product name	Version
X2E GmbH	http://www.x2e.de	Xoraya

File format	Comment
*.asc
*.mf4	BUSACCESS - CAN(-FD) ports support MDF4 bus logging only. XCP ports support signal-based MDF4 recording.
*.pcapng	BUSACCESS - CAN(-FD) ports will use linktype=227. The resulting files cannot be processed by trace analysis.

Operating system	Support
Windows	✓
Linux

Ports¶

Specifics¶

Notes regarding gen5 loggers (N series)

With the latest generation of loggers (e.g. Xoraya N8000) the recording needs to be configured completely on the logger itself. Choice of file format or restriction to certain busses in ecu.test has no effect.

For controlling the recording in this case, best use the Jobs StartLogging, StopLogging, GetLastSessions and FetchTrace.

In order to read bus and ethernet data “live” in the test case with such loggers, PLP can be used. To achieve this, the logger needs to be configured to output the desired data as PLP on a network interface, and in ecu.test the corresponding ports of the tracetronic: Ethernet tool adapter can be used to receive and interpret that data.

All subsequent information applies to “classic” loggers (V4, V5, Z7, as well as N series running gen4 firmware)

This interface allows, by means of hardware, direct CAN and FlexRay bus access. It supports the test steps read signal, read/write signal group (all bus systems) as well as monitor (CAN only) and supports signal recording (all bus systems), Raw diagnostics with KWP2000 over ISO-TP (CAN only), the Mini residual bus simulation (CAN only) and Additional functions of the close-to-hardware bus connections (all bus systems).

Info

The APPLICATION ports can only be used with the Add-on ecu.test calibration

Additionally it supports recording bus activity on the logger’s hard disk with subsequent download to DLF, BLF and/or ASC files, either individually for each bus / port, or jointly across all connected buses, as a tool log recording.

Caution! In direct bus access mode this interface tends to receive bus messages with considerable delay. It is not particularly well suited for checking time constraints in the test case. The time stamps in signal recordings (both “online” on the PC and “offline” on the logger) are still correct. Thus the analysis of temporal behavior using the trace analysis is not affected. However, when recording on the PC, the contents of the recording may end considerably earlier than expected.

If a configuration file is specified, it must have been created with Xoraya Suite 2.1. Settings saved using other versions might not be loaded correctly.

If you use BLF as output format, a copy of the file binlog.dll must exist in the %windir%/System32/ directory. The file can be obtained from Vector Informatik GmbH. Correct operation is tested with version 3.5.0.1 of binlog.dll. Earlier versions can possibly lead to program crashes or other misbehaviour.

If you use DLF as output format, the downloaded recordings will not be renamed for technical reasons. The filename stated in the test report will be generally wrong.

Downloading via tool jobs is only possible, if no direct bus access port (including restbus simulation, raw diagnostics, or J1939) is currently started. This is the case if either no such port exists in the current test bench configuration, or if the current test configuration uses none of those ports, or if none of the the current test case’s test steps and signal recordings accesses such a port.

If several offline recordings are started and stopped in an interleaved scheme, all recordings contain the complete data traffic from the first start until the last stop.

Simultaneous use of several offline recording types (tool job, log recording, signal recording) is not possible.

Properties 🛈¶

Name	Default value	Valid values	Type	Description
Hardware		[‘<online query>’, ‘<no toollib start>’]	string	Choose the hardware which should be used
Export formats	‘ASC’	[‘ASC’, ‘BLF’, ‘DLF’, ‘PCAP’, ‘ASC, BLF’, ‘ASC, DLF’, ‘ASC, PCAP’, ‘BLF, DLF’, ‘BLF, PCAP’, ‘DLF, PCAP’, ‘ASC, BLF, DLF’, ‘ASC, BLF, PCAP’, ‘ASC, DLF, PCAP’, ‘BLF, DLF, PCAP’, ‘ASC, BLF, DLF, PCAP’]	string	Save log recordings in these formats
DLF version		[ONLINE]	string	Version of the DLF format to use
DLF splitting size	‘100M’		string	Size in bytes at which DLF files will be split. Suffixes K, M and G may be used. Enter nothing to allow DLF files of arbitrary size.
New DLI for each DLF	☐		bool	Defines whether a separate DLI file should be created for each DLF file.
Stop recording	☐		bool	Stop recording on connection if still running?
Configuration file			string	Configuration file with channel settings etc.
Save configuration persistently	☐		bool	Save the loaded configuration file into the logger’s nonvolatile memory?
Timeout for tool call ❲in sec.❳	‘600’		string	Timeout after which a tool call is aborted.

Jobs 🛈¶

DeleteSessions¶

Delete traces from the logger HDD

Parameter

Name	Available if	Default value	Valid values	Type	Description
firstSession		0		int	Number of the first session to delete
lastSession		0		int	Number of the last session to delete

FetchTrace¶

Fetch a trace from the logger’s HDD. Only possible of no (live) bus access port is started.

Parameter

Name	Default value	Valid values	Type	Description
bus	‘ALL’	[‘ALL’, ‘CAN’, ‘FLEXRAY’, ‘LIN’, ‘ETHERNET’, ‘MOST25’, ‘MOST150’, ‘RS232’, ‘ANALOG’]	string	Write only this bus type into the trace file
controller	0		int	Write only this channel into the trace file. 0=all.
DLFVersion		[ONLINE]	string	Version of the DLF format to use
firstSession	0		int	Number of the first session to export
fmt	‘ASC’	[‘DLF’, ‘BLF’, ‘ASC’, ‘PCAP’, ‘DLF, BLF’, ‘DLF, ASC’, ‘DLF, PCAP’, ‘BLF, ASC’, ‘BLF, PCAP’, ‘ASC, PCAP’, ‘DLF, BLF, ASC’, ‘DLF, BLF, PCAP’, ‘DLF, ASC, PCAP’, ‘BLF, ASC, PCAP’, ‘DLF, BLF, ASC, PCAP’]	string	Save trace in these formats
lastSession	0		int	Number of the last session to export
newDliOnMaxFileSize	☐		bool	Defines whether a separate DLI file should be created for each DLF file.
splitSize	‘100M’		string	Size in bytes at which DLF files will be split. Suffixes K, M and G may be used.
targetFile			string	Path to target file

FormatLoggerHdd¶

Format the logger HDD

GetLastSessions¶

Requests the number area of the last record. Returns: tuple (firstSession, lastSession).

Restart¶

Restarts the Xoraya logger. Live bus access will not work anymore until the next test case is executed. It is recommended to use this job at the end of a test case.

Parameter

Name	Available if	Default value	Valid values	Type	Description
ReconnectDelay		10		int	Number of seconds to wait before each attempt to re-establish a connection to the logger after issung a restart command
ReconnectRetries		3		int	Number of attempts to re-establish a connection to the logger after issuing a restart command

StartLogging¶

Start recording

StartProbeStreaming¶

Start probe streaming

StopLogging¶

Stop recording

StopProbeStreaming¶

Stop probe streaming