A long time it was considered as impossible to operate Ethernet in the car over unshielded cables. Nevertheless, one wanted to utilize the advantages of Ethernet for application in the automotive sector: Speed and significantly lower costs convinced to check the possibility of using Ethernet now for automotive applications. It shows, that such a use is possible; at first it was the BroadR Reach technology of Broadcom that has considerably contributed to.
From this common interest, the OPEN Alliance (One-Pair Ether-Net) Special Interest Group (SIG) was established as a consortium of automobile manufacturers, technology vendors and other partners from the field of the automobile. The impressive number of more than 200 members demonstrates the confidence that is now set in the use of Ethernet in the automotive sector.
The Open Alliance aims, amongst others, to achieve a wide acceptance of Ethernet networks. Such wide scale adoption is achieved mainly through the establishment of common developed standards with general rules and guidelines for the implementation of Ethernet networks in the automobile.
The standards as basic rules offer at the same time security as they emerge from a long analysis process under consideration of possible operating situations and also are the indispensable basis for the interoperability of participants in an Ethernet network.
The following list gives an overview about our test solutions for Automotive Ethernet Integrated Devices.
OPEN Alliance Automotive Ethernet ECU Test Specification (TC8).
Automotive Ethernet includes the following ISO/OSI layers:
- Layer 1: Phyiscal Layer OPEN Alliance BroadR-Reach (OABR)
- Layer 2: Data Link Layer, e.g IEEE Ethernet MAC + VLAN (802.1Q), ARP
TCP/IP Protocol family
The TCP/IP Protocol family includes the following ISO/OSI layers:
- Layer 3: Network Layer, e.g. IP, ICMP
- Layer 4: Transport Layer, e.g. UDP, TCP, DHCP
The Automotive Protocols include the following ISO/OSI Layers:
- Layer 5-6-7: Application-oriented Layer, e.g. SOME/IP, SD
Robustness & Performance Tests
- RFC 2544
- RFC 2889
SWITCHES (IEEE 802.1Q)
- General switch requirements
- Address resolution
- Quality of Service (QoS)
If you are looking for individual solutions that can not be found in the list or if you need further information please contact us.
- At the IEEE Ethernet & IP @ Automotive Tech Day, October 27 – 28 in Yokohama, Japan, our employee Fabian Nikolaus gave a lecture about the standardization of tests for efficient testing of Automotive Ethernet ECUs. Here you can download the presentation.
- At the 2015 OPEN all member meeting October 26 and the IEEE Ethernet & IP @ Automotive Tech Day, Booth #C3, October 27 – 28 in Yokohama, Japan physical layer transceivers (PHYs) of different vendors were shown working together in a single platform. Our employee Ricardo Sappia describes his impression:
During the OPEN All Member F2F and the Ethernet & IP @ Automotive Technology Day held at Yokohama, Japan we had a great opportunity to show the first interoperable demonstration in a BroadR-Reach (100BASE-T1) ecosystem where different silicon vendors and cable assemblies coexisted with an interoperable behavior. This fact reflects for sure a major milestone in the progress of the Automotive Ethernet field. We were happy to see the great interest generated by this demonstration during the event and also to know that C&S Group helped to make it happen!
Then please read under Best Practice, what the benefits are and what you can expect from us!
For detailed information about our test solutions for Automotive Ethernet PHYs and switches, please refer to the following sections.
If you have further questions, please contact us. Here you can find our contact information.
The precondition for the communication between components in a network is their ability to work together. This is today a challenge in most networks especially because components of different manufacturers must function with each other – without adjusting them separately again during installation.
The basic requirement for this interoperability is the existence of detailed and comprehensive standards as basic rules for the behavior of the components in the network.
The compliance with these standards by the components of a network is mandatory to ensure safe operation of the network – and the related applications.
The test of whether a component complies with the underlying standard is a component of interoperability testing: Ethernet IOPT (InterOPerability Test) describes our interoperability tests for automotive Ethernet.
With these tests we want to make sure that interconnected components that use OABR-able PHYs (OPEN Alliance BroadR-Reach-able physical interfaces), are going to work together with the highest probability of interoperable behavior.
To all our tests, we take the basic rules that are/will be defined for the components in Ethernet networks as a basis. Thereby we lay the focus on layer 1 of the OSI layer model and on the virtually ’lying underneath’ transmission medium. Does the PHY follow the defined rules of the standards? Does the interaction of multiple PHYs vendors work in a reliable way? While the first question aims the confirmation of the standard compliant implementation of the PHY, the second question considers the standard itself: Does it have gaps? Are there applications in which there would be no secure solutions?
Besides the following summarized information, you will find in our article by Dip.-Ing. Ricardo Sappia Enabling Interoperability in a Multi-vendor Environment of BroadR-Reach PHYs a detailed description of the principles and the implementation of Ethernet IOPT.
The Ethernet IOPT test system consists essentially of three main elements:
- Link Partner
- Test Supervisor
The Test Supervisor coordinates the test procedures and collects the information, obtained during the tests. From these records he later derives the test result.
The component to be tested (DUT = Device Under Test) and the Link Partner support the test coordination and provide valuable information about internal registers, channel quality and current status.
Ethernet IOPT involves essentially three sets of tests:
- Group 1
The test cases of this group ensure that the PHY signals the correct link state to upper layers. In particular, a PHY must not signal an active link when no data can be transmitted.
- Group 2
The test cases defined in this group shall ensure that the PHY is able to establish an active link after reset and reconfiguration of itself, or of the link-partner’s PHY).
- Group 3
The test cases defined in this group shall ensure that optional PHY features, such as an estimation of the channel quality or cable diagnostics, provide expected and comparable results under known test conditions. If a PHY supports a given feature, the associated test cases are mandatory. Else, the test case shall be ignored.
The tests do not only affect the respective PHY alone, but also consider the circumstances that affect the behavior of the PHY – including, of course, the configuration of the PHY, but also the ‘environmental parameters’, arising from the use of the PHY in a network.
The results of the interoperability tests depend not only on the PHY to be the test itself, but also on the parameterization and configuration of its environment. From this fact there results a nearly infinite number of test cases.
The selection of relevant test cases from these possible test cases is of great importance and is based on the results of the working groups of the Open Alliance and on our many years of experience in the field of testing.
Members can already get the OPEN Alliance IOPT specification; it will also be released later. More information is available on the web page of the OPEN Alliance.
Successful assessment of our QM system.
On March 10, 2017, we had a representative of the DAkks in our house, who has carried out a monitoring report on our cur
We were at the “Automotive Ethernet Congress” on the 7th of February 2017
This year „Automotive Ethernet Congress” took place in Hilton Munich Park near the English Garden in Munich. Like la
Presentation at the iCC in Nuremberg on March 8, 2017
On Wednesday, March 8th, 2017, our employee, Christoph Wosnitza, gave a presentation on "Interoperability challenges for