Thursday, July 30, 2026

When France Said No: How India Turned GaN Technology Denial into a Semiconductor Opportunity - joining the dots...



There is a fascinating story unfolding in India's semiconductor journey—one that begins not in a commercial semiconductor fab, but around the strategic technology negotiations associated with the Rafale era.

At the centre of the story is a deceptively small piece of semiconductor technology:

Gallium Nitride — GaN.

Today, GaN is one of the most strategically important semiconductor technologies for high-frequency and high-power electronics. It can be used in radar, electronic warfare, satellite communications, telecom infrastructure and advanced power electronics.

And India's journey towards mastering it illustrates an important principle of technological sovereignty:

When a critical technology cannot be bought, the alternative is to learn how to build it.

The first dot: technology denial

During the Rafale negotiations, reports have circulated that India sought access to advanced GaN semiconductor technology associated with French defence electronics, but that the sensitive technology itself was not transferred.

The important distinction is between buying a finished component and acquiring the know-how to manufacture the underlying technology.

The former creates a customer.

The latter creates technological capability.

Public reporting on the Rafale-era episode is not accompanied by a publicly available French government document establishing every detail of the alleged request and refusal, so the claim should be treated cautiously. But the broader technology-denial narrative has been widely reported.

And then something important happened.

India did not remain dependent on imported GaN technology.


The second dot: DRDO starts building the capability

India's Defence Research and Development Organisation pursued indigenous GaN technology through its semiconductor research ecosystem.

The Solid State Physics Laboratory (SSPL) and Gallium Arsenide Enabling Technology Centre (GAETEC) worked on GaN semiconductor devices and MMICs.

By March 2023, GaN MMICs fabricated through this ecosystem had successfully undergone functionality testing. The development was significant because GaN MMICs are particularly relevant to high-frequency defence applications.

By 2024, DRDO had also announced indigenous work involving GaN HEMTs, alongside development of 4-inch silicon-carbide wafers. The reported GaN devices reached power levels up to 150 W.

This is much more significant than merely producing "a chip".

A modern radar or electronic-warfare system requires an entire RF semiconductor technology chain:

materials → epitaxy → transistor → MMIC → RF module → antenna system → radar/EW platform

Controlling more of that chain means controlling more of the technology.


But DRDO is only half the story

Here is where the story gets really interesting.

A defence laboratory can demonstrate a technology.

But a nation does not achieve semiconductor sovereignty simply by producing a successful laboratory prototype.

The technology has to escape the laboratory.

It needs:

research → manufacturing → testing → qualification → products → customers → scale

And that brings us to IISc and AGNIT Semiconductors.


The third dot: IISc's long GaN journey

Long before India's current semiconductor boom, researchers at the Indian Institute of Science (IISc), Bengaluru, had been working on GaN technology.

AGNIT says its technology base comes from more than 17 years of GaN research at IISc. The company emerged as an IISc spin-off in 2021. By 2022 it had sold its first wafers and developed RF prototypes, followed by commercial RF devices in 2023.

This is an extremely important distinction.

AGNIT isn't simply an Indian company assembling imported GaN components.

It describes itself as a fab-lite GaN semiconductor company, developing GaN wafers, components and modules for telecommunications, defence and strategic applications.

In other words:

Indian research → Indian IP → Indian startup → Indian GaN products.

That is the missing bridge between laboratory research and industrial capability.


The fourth dot: AGNIT starts building the industrial layer

The development becomes even more interesting in 2026.

AGNIT has established a ₹3-crore GaN testing and qualification laboratory at IISc Bengaluru.

The facility includes environmental testing capability from −60°C to +125°C, RF measurement equipment, connectorised load-pull testing and automated PCB assembly capability.

Why is testing so important?

Because making a transistor is not the same thing as making a reliable semiconductor product.

A defence or telecom customer needs to know:

  • Does the device work across temperature?
  • How stable is it?
  • How much RF power can it deliver?
  • What happens under stress?
  • How does manufacturing variation affect performance?
  • Can thousands of devices meet the same specification?

Qualification infrastructure is therefore part of semiconductor sovereignty.

AGNIT is effectively building another piece of that ecosystem.


Now connect the dots

Look at the sequence:

1. Strategic technology becomes inaccessible

GaN technology is considered strategically sensitive.

2. India develops indigenous capability

DRDO/SSPL/GAETEC work towards indigenous GaN MMIC and device technology.

3. Indian academic research matures

IISc spends years developing GaN materials, devices and fabrication expertise.

4. Research becomes entrepreneurship

AGNIT emerges as an IISc spin-off.

5. The startup develops actual products

AGNIT moves from wafers and prototypes to commercial RF devices.

6. Qualification infrastructure appears

AGNIT establishes its own GaN testing and qualification laboratory at IISc.

7. Defence and telecom become markets

GaN becomes relevant not only to strategic systems but also to telecom and other high-power/high-frequency applications.


And there is one more important dot

The Indian semiconductor story is no longer restricted to individual laboratories or startups.

The government is attempting to create a broader semiconductor manufacturing ecosystem.

That matters because a semiconductor startup cannot become strategically important if the surrounding manufacturing ecosystem doesn't exist.

You need:

  • wafer fabrication
  • epitaxy
  • packaging
  • testing
  • qualification
  • equipment
  • materials
  • skilled engineers
  • government procurement
  • private capital
  • large customers

Only when these pieces connect does a country move from:

"We can design it."

to

"We can make it."

and eventually:

"We control the technology."


The AGNIT story is therefore bigger than one startup

AGNIT's importance isn't simply that it is producing GaN devices.

It represents a possible technology-transfer pipeline from Indian scientific research into industry.

Think of the architecture:

IISc


fundamental research

Indian semiconductor process technology

AGNIT


commercial products

Defence / Telecom / Space / RF systems

That is precisely the kind of ecosystem India needs.

And this is why the story should not be reduced to:

"France refused to give India GaN technology."

The much bigger story is:

India developed the scientific capability to reproduce and commercialise a strategically important technology instead of remaining permanently dependent on the country that possessed it.


France and India: the irony

There is also an interesting geopolitical twist.

France and India today have an increasingly deep strategic relationship.

So this isn't really a story about India "defeating France".

It is a story about strategic autonomy changing the nature of partnerships.

A technologically dependent country negotiates from a position of weakness.

A technologically capable country can collaborate from a position of strength.

That distinction matters enormously in defence.


From buyer to technology partner

This is ultimately what India's semiconductor strategy should be about.

Not merely:

"How many fabs can India build?"

But:

"How many critical technologies can India understand deeply enough that denial no longer cripples us?"

GaN is a perfect example.

A technology that was once difficult to access becomes an Indian research problem.

The research becomes an Indian engineering capability.

The engineering capability becomes a startup.

The startup develops products.

Products enter strategic markets.

And the surrounding ecosystem begins to grow.

That is how technological sovereignty is built.

Not overnight.

Not through slogans.

But through 15–20 years of scientific research, engineering, failed experiments, prototypes, manufacturing, testing, capital and persistence.


The real lesson

The most important line in this entire story may therefore be:

Technology denial can delay technological progress. It does not necessarily prevent it.

India's GaN journey illustrates something deeper about national technological development.

DRDO brings strategic mission and defence requirements.

IISc provides deep scientific research.

AGNIT provides the entrepreneurial bridge.

Capital provides scale.

Testing and qualification provide industrial credibility.

Government policy provides ecosystem support.

And the final objective is not merely to manufacture a GaN chip.

It is to create an ecosystem in which the next generation of strategic semiconductor technology can be developed inside India.

That is the real meaning of semiconductor sovereignty.

And perhaps the most fascinating part of the story is this:

The answer to "Can India build it?" is increasingly becoming — "Give the Indian scientists enough time."

Wednesday, July 29, 2026

When a Bridge Becomes a PhD: Is China Redefining Doctoral Education?

For generations, the image of a PhD has remained almost unchanged.

Years of research. Hundreds of pages of dissertations. Endless citations. A thesis read by only a few experts.

But what if a doctorate could be earned by building something that changes the real world instead?

China is testing that idea.

A Different Definition of Research

Under 2024 reforms, selected Chinese universities can award engineering doctorates based on practical technological achievements, not just dissertations.

Instead of “What did you write?”, the question becomes:

“What did you build that works?”

The First Graduates

The results are already drawing attention.

Zheng Hehui designed interlocking steel blocks used in the Changtai Yangtze River Bridge, the world’s longest cable-stayed bridge.

Wei Lianfeng developed vacuum laser welding techniques for China’s nuclear industry.

Others have built firefighting systems for seaplanes and solved major industrial engineering problems.

Their theses are now working technologies.

Bridging Academia and Industry

A long-standing issue in engineering education is the gap between research and industry.

Universities reward papers. Industry rewards products.

China’s programme aims to merge the two.

Since 2022, over 60 universities and about 100 companies have joined, with thousands of students working on industry-linked doctorates in fields like AI, semiconductors, aerospace, and energy.

Is This Really New?

Not entirely.

Many countries already have industry PhDs and professional doctorates.

The difference is scale: a deployed technology or prototype can now serve as the core proof of a doctorate, not just a written thesis.

The Potential Advantages

  • Solves real industrial problems
  • Speeds up technology transfer
  • Strengthens university–industry ties
  • Prepares engineers for real-world innovation
  • Emphasises measurable impact

But There Are Challenges

Traditional PhDs create a permanent academic record.

A prototype may not fully explain why it works or advance theory in the same way.

Key questions remain:

  • How is originality judged?
  • How is work verified?
  • What ensures academic rigour?
  • Does secrecy limit openness?

This model may complement, not replace, traditional PhDs.

Should Other Countries Follow?

Many countries already have strong dissertation-based systems that drive major scientific breakthroughs.

But engineering ultimately meets practice.

The future may require both:

  • rigorous research
  • and real-world impact

A bridge that lasts decades may represent knowledge as much as a written thesis.

Final Thoughts

China’s experiment challenges the idea that a dissertation is the only path to a PhD.

Whether it spreads globally is unclear. But it raises a key question:

In engineering, should we value pages written—or problems solved?

Perhaps the best PhDs combine both.

From Bharat's perspective...

My POV...

Monday, July 20, 2026

Vimag Labs’ Magnetless Motor Breakthrough: India’s Software-Defined Challenge to Rare-Earth Dependence...

 In the electric vehicle (EV) world, rare-earth permanent magnets have long been the hidden bottleneck. They deliver the high efficiency and torque that power most modern EVs, but they come with massive supply-chain risks—China dominates ~90% of rare-earth processing and a huge share of the high-performance NdFeB magnets used in motors.

A Bengaluru-based deep-tech startup called Vimag Labs (sometimes associated with the Volektra brand) claims to have cracked a compelling alternative: a Virtual Magnet Synchronous Motor (VMSM) that eliminates rare-earth magnets entirely by using software, power electronics, and clever electromagnetic design.

What Is a Magnetless (or “Virtual Magnet”) Motor?

Traditional Permanent Magnet Synchronous Motors (PMSMs) embed strong rare-earth magnets in the rotor. These create a fixed magnetic field that interacts with the stator’s rotating field to produce torque. It’s efficient, compact, and powerful—but dependent on critical minerals.

Vimag’s VMSM removes those physical magnets. Instead:

  • It uses a brushless, slip-ring-free architecture.
  • A rotating transformer (patented) wirelessly transfers power to the rotor.
  • Proprietary control algorithms and power electronics dynamically generate and control the rotor’s magnetic field in real time—essentially creating a “virtual magnet” whose strength and behavior can be tuned on the fly.

The result, according to the company, is a synchronous motor that matches or exceeds the performance of traditional PMSM designs in efficiency, torque, and power density—while using only common materials like copper and steel.

The Latest Milestone: Fifth Indian Patent

In July 2026, Vimag Labs was granted its fifth Indian patent, titled “A Robust Rotating Transformer Excited Synchronous Motor and Its Control.” This protects the core architecture of the VMSM platform.

The company now has:

  • 5 granted patents
  • 10 additional patent applications
  • 15 trademarks

This IP covers motor design, software controls, power electronics, and application-specific tweaks. CEO and co-founder Manish Seth (with prior experience at Volkswagen, Ford, and GM) noted the patent represents over 87,600 engineering hours.

Why This Matters — Strategic and Commercial Angles

Supply Chain Independence
By going magnet-free, Vimag reduces exposure to geopolitical risks and price volatility in rare-earth materials. This is especially relevant for India and any nation seeking to localize EV manufacturing.

Cost and Flexibility
No rare-earth magnets can lower bill-of-materials costs. The software-defined nature also opens the door to performance improvements via firmware updates rather than hardware redesigns.

Target Applications

  • Two-wheelers and passenger vehicles (current pilots)
  • Light & heavy commercial vehicles
  • Industrial systems (200–600 kW)
  • Robotics, defense, and cooling systems

Vimag recently raised $5 million in Series A funding led by Accel, with participation from Chakra Growth Fund and Thinkuvate. They’ve also signed a manufacturing MoU with Jendamark to support scale-up.

Challenges and Realistic Outlook

This is still early-stage technology. While the claims are impressive—matching or beating PMSM performance without magnets—the technology has not yet been independently verified at full production scale. Many magnetless or reduced-rare-earth approaches (induction motors, switched reluctance motors, etc.) have historically traded off efficiency, torque density, or added complexity like brushes/slip rings.

Vimag’s brushless rotating-transformer approach aims to avoid those classic downsides. Success will depend on real-world validation in pilots, thermal management, long-term reliability, and cost at volume.

The Bigger Picture

Vimag Labs, founded in September 2025, is part of a growing wave of innovation seeking to make EVs less dependent on a handful of critical materials. If the VMSM platform delivers on its promises, it could accelerate India’s (and the world’s) ability to build high-performance electric motors domestically—using software smarts instead of imported magnets.

The road from promising patent to mass-market adoption is long, but the direction is exciting: turning the motor itself into a software-defined component.

Watch VIMAG...

I am sure it will be worthy your time...

Jai Hind...

The Fragility of Time: NavIC Clocks, White Rabbit, and Bharat’s Path to True Digital Sovereignty...

The word Vishwaguru (a global leader) implies self-sufficiency—the ability to stand tall on homegrown foundations without critical single points of failure. Yet, when we examine the backbone of modern digital civilizations—Timing and Navigation—a sobering technical truth emerges.

Without microsecond-level synchronization, modern power grids fail, 5G networks drop calls, stock markets lose trade order, and guided systems drift off-target.

The recent setbacks faced by India's NavIC (Navigation with Indian Constellation) due to atomic clock failures, contrasted with our rollout of ground-based White Rabbit technology, offer a masterclass in why Bharat must secure its hardware stack from the silicon layer up.

1. The NavIC Dilemma: Space-Segment Timing Fragility

Satellite navigation systems (GNSS) don't actually measure distance; they measure time. A receiver calculates its position on Earth by measuring the fraction-of-a-nanosecond delay of signals traveling at the speed of light from multiple orbiting satellites via trilateration.

If a satellite's onboard clock drifts by even 1 microsecond, your ground position calculation errs by 300 meters.

[Satellite 1]     [Satellite 2]     [Satellite 3]     [Satellite 4]
    \                 |                 |                 /
     \                |                 |                /
      +---------------+-----------------+---------------+
                              |
                     [Ground Receiver]
             Requires ≥ 4 valid clocks for (X, Y, Z, t)

To achieve precise Position, Navigation, and Timing (PNT), a constellation needs a minimum of 4 operational satellites with healthy atomic clocks.

Where the Bottleneck Occurred

  • The Dependency Trap: Early IRNSS satellites relied on imported RAFS (Rubidium Atomic Frequency Standard) clocks. When these imported units began failing prematurely in orbit, entire satellites were rendered functionally useless for PNT, despite having healthy propulsion and solar arrays.
  • The Replenishment Race: While ISRO successfully developed indigenous rubidium clocks for the second-generation NVS-01 satellite, hardware supply chain delays and launch anomalies (such as NVS-02 failing to reach its intended orbit) mean replenishment couldn't keep pace with the degradation of aging space hardware.

The lesson is stark: You cannot claim strategic autonomy in space if your core timing mechanism rests on foreign components.

2. White Rabbit: The Terrestrial Ground Truth

While space-based timing faces orbital hurdles, India has taken a major step forward on the ground with White Rabbit (WR) technology under the One Nation, One Time initiative.

Originally engineered at CERN, White Rabbit is an open-source extension of Ethernet (IEEE 802.3) and the Precision Time Protocol (PTP / IEEE 1588). It synchronizes clocks over fiber-optic networks with sub-nanosecond precision.

                       [CSIR-NPL / UTC(NPLI)]
                         (Primary Time Standard)
                                   |
                         [WR Grandmaster Switch]
                                   |
             +---------------------+---------------------+
             | (Fiber Optic)                             | (Fiber Optic)
             v                                           v
   [NSE / BSE Trading Engine]                   [5G Core & Cell Towers]
   Timestamping: < 1 nanosecond                 Phase Sync: < 1.5 microseconds

How White Rabbit Works

WR achieves sub-nanosecond synchronization by combining two core techniques:

  1. Synchronous Ethernet (SyncE): The receiving node locks its physical layer clock frequency directly to the transmitter's bitstream, eliminating clock frequency drift.
  2. DDMTD Phase Detection: Dual-Mixer Time-Difference circuits measure the phase offset between transmitted and reflected signals down to picoseconds, continuously adjusting for temperature-induced fiber latency variations.

Deploying WR nodes across national stock exchanges (like the NSE), power grids, and telecom networks decouples critical ground infrastructure from external space-based GNSS signals (like US GPS), protecting them against satellite failures, jamming, or spoofing.

3. The Grand Gap: Why Ground Timing Isn't Enough

While White Rabbit secures stationary ground nodes, it cannot guidance-control an airborne vehicle, assist a naval vessel in open ocean, or serve mobile smartphones. Ground-based fiber networks and space-based constellations are two halves of the same sovereign coin.

True digital sovereignty requires mastering the entire spectrum:

LayerTechnologyCurrent StatusSovereign Goal
Terrestrial NetworkWhite Rabbit / SyncEActive rollout across NPL & exchangesNationwide WR fiber ring for UPI, 5G, & Grids
Space-Segment ClocksRubidium / Cesium StandardsTransitioning from imported to ISRO RAFS100% space-qualified indigenous atomic clocks
Silicon & FabNavigation Baseband ICsMixed; reliance on foreign foundriesDomestic fab production of radiation-hardened ICs
User EcosystemSmartphone Baseband ChipsGrowing L5/L1 NavIC adoptionMandated dual-frequency NavIC in all domestic hardware


4. Before Vishwaguru: The Blueprint for Real Digital Autonomy

For Bharat to be a true technological leader, we must bridge the gap between intent and execution across critical infrastructure:

  1. Foundational Component Independence: Developing indigenous atomic clocks is a huge step forward, but we must also control the underlying semiconductor fabrication. A home-designed clock printed on foreign silicon remains vulnerable to geopolitical chokepoints.
  2. Constellation Redundancy & Fast-Track Logistics: Replenishment pipelines for space assets must be agile. When a satellite clock degrades, replacement payloads must be ready for rapid launch rather than waiting through multi-year assembly backlogs.
  3. Hardware-Level Integration: White Rabbit must be mandated across all critical national infrastructure—from regional load dispatch centers to banking cores—creating an unshakeable ground truth for Indian Standard Time (IST).

Final Thoughts

The failure of an orbiting clock or a launch insertion is not a cause for cynicism; it is a hard-engineering reality check. True sovereignty is built by facing these failure modes head-on.

By combining the terrestrial precision of White Rabbit with a resilient, 100% indigenized NavIC space segment, Bharat can build a timing and navigation architecture that is truly unshakeable—from the fiber in our ground to the orbits overhead.

Friday, July 3, 2026

Bridge Pattern using Python...

Bridge Pattern is a structural design pattern that decouples an abstraction from its implementation, allowing both to evolve independently.

Why it exists (The Problem)When you have classes that can vary in two or more independent dimensions, simple inheritance leads to a combinatorial explosion of subclasses.
Example:
  • You have shapes: Circle, Square
  • You have rendering APIs: OpenGL, DirectX, Vulkan
Using inheritance, you end up with: CircleOpenGL, CircleDirectX, SquareOpenGL, etc. — and it gets worse as you add more shapes or renderers.Solution: Bridge PatternThe pattern splits the class into two hierarchies:
  1. Abstraction – High-level control logic (e.g., Shape)
  2. Implementation – Low-level platform-specific details (e.g., Renderer)
These two hierarchies are connected via a bridge (composition instead of inheritance).
Here is a Python implementation of the Bridge Pattern.



from
abc import ABC, abstractmethod

# ==================== Implementor 1: Color ====================
class Color(ABC):
@abstractmethod
def get_color(self) -> str:
pass

@abstractmethod
def paint(self):
pass


class Red(Color):
def get_color(self) -> str:
return "Red"

def paint(self):
print("Painting the vehicle in vibrant Red...")


class Black(Color):
def get_color(self) -> str:
return "Black"

def paint(self):
print("Painting the vehicle in deep Black...")


# ==================== Implementor 2: Gear ====================
class Gear(ABC):
@abstractmethod
def get_type(self) -> str:
pass

@abstractmethod
def shift(self):
pass


class ManualGear(Gear):
def get_type(self) -> str:
return "Manual"

def shift(self):
print("Shifting gears manually...")


class AutoGear(Gear):
def get_type(self) -> str:
return "Automatic"

def shift(self):
print("Shifting gears automatically...")


# ==================== Abstraction: Vehicle ====================
class Vehicle(ABC):
def __init__(self, color: Color, gear: Gear):
self.color = color # Bridge to Color implementor
self.gear = gear # Bridge to Gear implementor

@abstractmethod
def display(self):
pass

def paint_vehicle(self):
self.color.paint()

def change_gear(self):
self.gear.shift()


# ==================== Refined Abstractions ====================
class SmallCar(Vehicle):
def display(self):
print(f"=== Small Car ===")
print(f"Color: {self.color.get_color()}")
print(f"Gear: {self.gear.get_type()}")
self.paint_vehicle()
self.change_gear()
print("Driving smoothly in the city...\n")


class Truck(Vehicle):
def display(self):
print(f"=== Truck ===")
print(f"Color: {self.color.get_color()}")
print(f"Gear: {self.gear.get_type()}")
self.paint_vehicle()
self.change_gear()
print("Hauling heavy load on the highway...\n")


# ==================== Client Code ====================
if __name__ == "__main__":
# Create implementors
red = Red()
black = Black()
auto = AutoGear()
manual = ManualGear()

# Create vehicles with different combinations (independent variation)
print("Creating vehicles using Bridge Pattern:\n")

car1 = SmallCar(red, auto)
car1.display()

car2 = Truck(black, manual)
car2.display()

car3 = SmallCar(black, auto)
car3.display()

Here's what the above solution would look like without the Bridge Pattern - look at the image below.

Look at the left-side hierarchy of classes. With more and more attributes, the inheritance tree would have exploded.

So... comes the Bridge Pattern - a nice solution without so many classes as depicted in the right hierarchy of classes.





I hope I have clarified the Bridge Pattern clearly.

Enjoy...