Automotive Ethernet Test Plans

The test plans on this page may be downloaded and used for internal purposes only. The test plans may not be commercialized in any way without express permission of the UNH-IOL.

The Automotive Ethernet testing service currently offers the following test plans. These documents are constantly being updated to improve readability and to reflect the current specifications. Please contact us if you would like more information or have questions about the Automotive Ethernet testing service.

When testing based on the following test plans is performed, all reports generated will be digitally signed using an Adobe digital certificate. Upon reception of the report, the recipient can verify its authenticity using our document validation instructions.

IOL

Conformance

Status
Fully Documented (Active)
Revision
2.0
Testing Days Needed
3 Days
Last Modified
2012-07-18
Abstract
This suite of tests has been developed to help implementers evaluate the functionality of their BroadR-Reach Physical Coding Sublayer (PCS) based products. This test suite covers both PCS Transmit and PCS Receive, including state diagrams, encoding/decoding, and scrambling/descrambling. The tests do not determine if a product conforms to the BroadR-Reach standard, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a PCS device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the UNH-IOL's interoperability test bed, these tests provide a reasonable level of confidence that the device under test (DUT) will function well in most environments.
Status
Fully Documented (Active)
Revision
2.0
Testing Days Needed
3 Days
Last Modified
2014-09-22
Abstract
These tests are designed to determine if a product conforms to specifications defined in OPEN Alliance BroadR-Reach Physical Layer Transceiver Specification For Automotive Applications Standard. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the UNH-IOL's interoperability test bed, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function properly in many BroadR-Reach automotive environments.
Status
Fully Documented (Active)
Revision
2.0
Testing Days Needed
3 days
Last Modified
2012-07-26
Abstract
These tests are designed to determine if a product conforms to electrical specifications of the BroadR-Reach transmitter and receiver defined in the BroadR-Reach standard. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the UNH-IOL's interoperability test bed, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function properly with many BroadR-Reach environments.
Status
Fully Documented (Active)
Revision
5.3
Testing Days Needed
3 days
Last Modified
2015-06-04
Abstract
This test suite deals with Reception issues such as CRC Errors, Framing Errors, Length Errors, Fragments, etc. as well as Transmission issues, proper spacing, proper preamble and SFD, For Half Duplex devices this also includes collisions, deference, etc. This suite of tests has been developed to help implementers evaluate the functioning of their Clause 4 Media Access Control (MAC) based products. The tests do not determine if a product conforms to the IEEE 802.3, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a MAC device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the IOL's interoperability test bed, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function well in most environments.
Notes
Previous versions of this test suite include: v4.1 v4.2 v4.3 v4.4 v4.5 v4.6, v5.0, v5.1, v5.2
1000BASE-X MAC Test Suites: v1.0, v2003_05_20.
Status
Draft (Active)
Revision
1.0
Testing Days Needed
Last Modified
2016-03-10
Abstract
This suite of tests has been developed to help implementers evaluate the functionality of their Clause 96 Physical Coding Sublayer (PCS) based products. The tests do not determine if a product conforms to IEEE 802.3 standard, nor are they purely interoperability tests. Rather, they provide one method to isolate problems within a PCS device. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the IOL's interoperability test bed, these tests provide a reasonable level of confidence that the device under test (DUT) will function well in most environments.
Status
Draft (Active)
Revision
1.0
Testing Days Needed
Last Modified
2016-03-10
Abstract
These tests are designed to determine if a product conforms to specifications defined in IEEE 802.3 Physical Layer Transceiver Specification For Automotive Applications Standard. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the UNH-IOL's interoperability test bed, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function properly in many 100BASE-T1 automotive environments.
Status
Draft (Active)
Revision
1.0
Testing Days Needed
Last Modified
2016-03-10
Abstract
These tests are designed to determine if a product conforms to specifications defined in the IEEE 802.3 standard. Successful completion of all tests contained in this suite does not guarantee that the tested device will operate with other devices. However, combined with satisfactory operation in the IOL's interoperability test bed, these tests provide a reasonable level of confidence that the Device Under Test (DUT) will function properly in many 100BASE-T1 environments.

Key

Fully Documented
Draft