Capabilities · Automotive Ethernet
100BASE-T1 and 1000BASE-T1 physical-layer checks, capture chains that keep VLAN tags and timestamps, SOME/IP and DoIP debugging, and gPTP time-sync validation, for ECU and vehicle-network teams in India.
From the twisted pair to the end-of-line station. Each card lights the point on the vehicle network where that work happens.
100BASE-T1 and 1000BASE-T1 run PAM-3 signalling over one twisted pair, at 66.67 MBaud and 750 MBaud. When a link drops, the cause is usually here.
Bench: PicoScope 6000E
A laptop NIC cannot join a 100BASE-T1 link, so capture starts with the right access method, chosen by how much the timing matters.
Bench: Wireshark 3.2+ (native SOME/IP)
Service discovery that finds nothing, routing activations that fail, diagnostic sessions that time out. Worked from the AUTOSAR and ISO specifications, not folklore.
Specs: AUTOSAR PRS · ISO 13400 · ISO 14229
When cameras, radar and control loops share one network, timing is something to validate, not assume.
Specs: IEEE 802.1AS · 802.1Qbv · 802.1DG
The Ethernet that carries SOME/IP in the vehicle also carries firmware images on the line. Through the ProMik partnership, validation and manufacturing speak the same network.
Bench: ProMik XDM-ETH
Vendor-neutral by design: every layer below is an IEEE, ISO or AUTOSAR specification. Each one names the discipline on this page that works there.
Worked on in 3 Diagnostics · 5 Production
AUTOSAR PRS
SOME/IP
Service-oriented communication and service discovery
ISO 13400
DoIP
Diagnostics over IP: discovery, routing activation, transport
ISO 14229
UDS
The diagnostic service layer, on DoIP or CAN
Worked on in 4 Time sync
IEEE 802.1AS
gPTP
One time base, from a grandmaster to every ECU
IEEE 802.1Qbv
TSN scheduling
Scheduled traffic: who transmits when
IEEE 802.1DG
Automotive TSN profile
Which TSN features an in-vehicle network uses
Worked on in 2 Capture
IEEE 802.1Q
VLAN
Tags that keep domains apart, and that captures must keep
IEEE 802.1AE
MACsec
Link-layer encryption between switches and ECUs
Worked on in 1 Physical layer
IEEE 802.3cg
10BASE-T1S + PLCA
Multidrop Ethernet reaching down into CAN territory
IEEE 802.3bw
100BASE-T1
100 Mbit/s over one twisted pair, the workhorse link
IEEE 802.3bp
1000BASE-T1
Gigabit single-pair Ethernet for cameras and backbones
IEEE 802.3ch
Multi-Gig T1
2.5, 5 and 10 Gbit/s for sensor and compute links
A laptop NIC cannot join a T1 link
Partner lines GSAS carries, with application engineering, INR invoicing and on-site set-up. Figures are the OEM's own, as published on each product page.
Pico Technology
Physical-layer work on T1 links: mask tests, edges and PAM-3 signal integrity.
ProMik
Ethernet-attached production programming for domain and zone controllers.
AutoPi
Vehicle network access in the field, with DoIP and CAN on one unit.
Checklist · PDF
Automotive Ethernet bring-up and validation checklist
The order GSAS works a new T1 bench in: link-up, physical layer, capture access, protocol, then time sync.
Related: CAN and LIN testing · Functional safety · Test and measurement · ProMik
Most teams arrive with one of these. Pick the one closest to yours.
01
New to automotive Ethernet
You have ECUs with T1 ports and a laptop that cannot see them. GSAS plans the capture access and gets the bench decoding real traffic.
02
Debugging an ECU or network
Links that drop, services that never appear, routing activations that fail. GSAS works the problem from the physical layer up until it has a root cause.
03
Zonal and domain architectures
Physical layer, protocol and time sync, validated as one programme, and carried through to Ethernet-attached production programming.
Tell us the link, the ECU or the symptom. GSAS engineers reply from India with how they would capture it, what they would measure, and the tooling it needs.
No. 100BASE-T1 runs PAM-3 over a single twisted pair, which a standard laptop NIC cannot join. Capture needs a media converter for interactive work, a switch mirror port when timing does not matter, or a hardware tap when it does.
Automotive 100BASE-T1 links usually run without auto-negotiation, so one end must be forced to master and the other to slave. After that, the usual causes are physical: cable, connector or termination faults on the unshielded pair, which show up on a scope long before they show up as protocol errors.
Wireshark has dissected SOME/IP natively since version 3.2. GSAS sets it up for SOME/IP, SOME/IP service discovery and DoIP, and builds capture chains that keep VLAN tags and timestamps intact.
DoIP (ISO 13400) is the transport: it finds the vehicle, activates routing and carries diagnostic messages over IP. UDS (ISO 14229) is the diagnostic service layer those messages belong to. UDS can also run over CAN.
On the bench: bring up the gPTP domain from a grandmaster across the switches, confirm every ECU achieves and holds sync, and diagnose losses caused by schedules and shapers. GSAS also checks that inline converters and taps are not biasing the very timestamps under test.
Engineering is led from Bengaluru, with offices in Chennai, Pune, Hyderabad, Mumbai and Delhi NCR among others, so support runs in Indian working hours.
Blog
Autonomy coverage fixates on perception. The engineers who deployed an autonomous haulage system describe something else: office software, truck software, and a wireless link whose performance decides how much centralisation the design can afford.
Agriculture is converging on an Ethernet future, with one preferred physical layer, because an implement from one maker has to plug into a tractor from another. Construction never had that forcing function, and the standard it does not have is a working condition.
Off-highway hardware-in-the-loop is established practice, built around hydraulics, implement dynamics and J1939. The machines have grown an Ethernet port. The bench upgrade is additive, and it is smaller than a rebuild.
India's machine builders are fighting the localisation battle in electronics, and electronics means a network: the J1939 backbone, the Ethernet arriving beside it, and the bench that has to see both.
A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.
Search for a 100BASE-T1 media converter and you get SKU pages that document their own DIP switches, plus a pile of copper-to-fibre converters that have nothing to do with single-pair automotive Ethernet. This is the selection guide neither publishes: what the box does at the PHY layer, when a converter is the wrong box, and the nine criteria that decide fitness, each written as a question to put to the supplier rather than a specification we invented. Standards claims trace to IEEE 802.3 task force records and the public OPEN Alliance specifications. Written by the GSAS Micro Systems engineering team in India.
