BorgWarner Secures Its First 48V Electric Cross Differential Program
- BorgWarner expands its 48V electric vehicle technology portfolio in China
- First 48V electric cross differential (eXD) program award in BorgWarner’s global portfolio
AUBURN HILLS, Mich., Feb. 11, 2026 /PRNewswire/ — BorgWarner has secured a new electric cross differential (eXD) program with a leading Chinese original equipment manufacturer (OEM). The eXD solution is designed for a 48V system and is integrated with the customer’s 48V electrical and electronic (E/E) architecture. This program represents BorgWarner’s first 48V eXD application within its global portfolio and expands the company’s torque management capabilities for electric vehicles.
As the electric vehicle market continues to evolve, E/E architectures are transitioning toward higher efficiency and greater integration. A 48V electrical architecture offers advantages including improved energy efficiency, optimized wiring and component costs, and support for higher-power applications. Leveraging this architecture, BorgWarner’s eXD is built to dynamically control torque distribution between wheels, enhancing vehicle handling and traction while maintaining a balance between performance, safety, and system efficiency.
“We believe BorgWarner’s eXD technology enhances handling and vehicle stability across a wide range of driving conditions,” said Isabelle McKenzie, Vice President of BorgWarner Inc. and President and General Manager, Drivetrain and Morse Systems. “Securing our first 48V eXD program demonstrates our ability to adapt proven torque management technologies to new electrical architectures. By leveraging a 48V system, the eXD is expected to improve energy utilization, system efficiency, and reliability, which will elevate the driving experience for electric vehicle users.”
BorgWarner’s eXD is engineered to dynamically adjust slip control based on real-time driving conditions and vehicle status, supporting vehicle stability during high-speed driving, rapid acceleration, and sharp turns. The eXD is also intended to deliver consistent handling performance across varying friction conditions. On dry roads, higher friction enables improved grip, and we expect this will allow the eXD to transfer more torque to the outer wheels for enhanced cornering performance. In low-friction environments such as ice, snow, or mud, the system is designed to rapidly detect wheel slip and limit torque transfer to slipping wheels, which will reallocate drive force to wheels with better traction to maintain stability and control.
About BorgWarner
For more than 130 years, BorgWarner has been a transformative global product leader bringing successful mobility innovation to market. With a focus on sustainability, we’re helping to build a cleaner, healthier, safer future for all.
Forward Looking Statements: This release may contain forward-looking statements as contemplated by the 1995 Private Securities Litigation Reform Act that are based on management’s current outlook, expectations, estimates and projections. Words such as “anticipates,” “believes,” “continues,” “could,” “designed,” “effect,” “estimates,” “evaluates,” “expects,” “forecasts,” “goal,” “guidance,” “initiative,” “intends,” “may,” “outlook,” “plans,” “potential,” “predicts,” “project,” “pursue,” “seek,” “should,” “target,” “when,” “will,” “would,” and variations of such words and similar expressions are intended to identify such forward-looking statements. Further, all statements, other than statements of historical fact, contained or incorporated by reference in this release that we expect or anticipate will or may occur in the future regarding our business strategy, goals, plans, references to future success and other such matters, are forward-looking statements. All forward-looking statements are based on assumptions and analyses made by us in light of our experience and our perception of historical trends, current conditions and expected future developments, as well as other factors we believe are appropriate under the circumstances. Forward-looking statements are not guarantees of performance, and the Company’s actual results may differ materially from those expressed, projected or implied in or by the forward-looking statements.
You should not place undue reliance on these forward-looking statements, which speak only as of the date of this release. Forward-looking statements are subject to risks and uncertainties, many of which are difficult to predict and generally beyond our control, that could cause actual results to differ materially from those expressed, projected or implied in or by the forward-looking statements. These risks and uncertainties, among others, include: the possibility that our 48V electric cross differential program will not achieve its intended benefits; the supply disruptions impacting us or our customers, commodity availability and pricing; competitive challenges from existing and new competitors; the challenges associated with rapidly changing technologies, including artificial intelligence, and our ability to innovate in response; potential future changes in laws and regulations, including, by way of example, taxes and tariffs, in the countries in which we operate; potential disruptions in the global economy caused by wars or other geopolitical conflicts; our dependence on automotive and truck production, which is highly cyclical and subject to disruptions; our reliance on major OEM customers; impacts of any future strikes involving any of our OEM customers and any actions such OEM customers take in response; fluctuations in interest rates and foreign currency exchange rates; our dependence on information systems; the uncertainty of the global economic environment; the uncertainty surrounding global trade policies, including tariffs and export restrictions, and their impacts on the Company, its customers and its suppliers; and the other risks discussed in reports that we file with the Securities and Exchange Commission, including in Item 1A, “Risk Factors” in our most recently-filed Annual Report on Form 10-K and/or Quarterly Report on Form 10-Q. We do not undertake any obligation to update or announce publicly any updates to or revisions to any of the forward-looking statements in this release to reflect any change in our expectations or any change in events, conditions, circumstances, or assumptions underlying the statements.
View original content to download multimedia:https://www.prnewswire.com/news-releases/borgwarner-secures-its-first-48v-electric-cross-differential-program-302684277.html
SOURCE BorgWarner Inc.
Potrebbe anche piacerti
Tether Backs Ark Labs’ $5.2 Million Bet on Bitcoin’s Stablecoin Revival
MySQL Single Leader Replication with Node.js and Docker
command: --server-id=1 --log-bin=ON The --server-id option gives each MySQL server in your replication setup its own name tag. Each one has to be unique and without it, replication won’t work at all. Another cool option not included here is binlog_format=ROW. This tells MySQL how to keep track of changes before passing them along to the replicas. By default, MySQL already uses row-based replication, but you can explicitly set it to ROW to be sure or switch it to STATEMENT if you’d rather log the actual SQL statements instead of row-by-row changes. \ Run our containers on docker Now, in the terminal, we can run the following command to spin up our database containers: docker-compose up -d \ Setting Up Our Master (Primary) Server To configure our master server, we would have to first access the running instance on docker using the following command docker exec -it mysql-master bash This command opens an interactive Bash shell inside the running Docker container named mysql-master, allowing us to run commands directly inside that container. \ Now that we’re inside the container, we can access the MySQL server and start running commands. type: mysql -uroot -p This will log you into MySQL as the root user. You’ll be prompted to enter the password you set in your docker-compose.yml file. \ Next, we need to create a special user that our replicas will use to connect to the master server and pull data. Inside the MySQL prompt, run the following commands: \ CREATE USER 'repl_user'@'%' IDENTIFIED BY 'replication_pass'; GRANT REPLICATION SLAVE ON . TO 'repl_user'@'%'; FLUSH PRIVILEGES; Here’s what’s happening: CREATE USER makes a new MySQL user called repl_user with the password replication_pass. GRANT REPLICATION SLAVE gives this user permission to act as a replication client. FLUSH PRIVILEGES tells MySQL to reload the user permissions so they take effect immediately. \ Time to Configure the Replica (Secondary) Servers a. First, let’s access the replica containers the same way we did with the master. Run this command in your terminal for each of the replica containers: \ docker exec -it <replica_container_name> bash mysql -uroot -p <replica_container_name> should be replace with the name of the replica container you are trying to setup b. Now it’s time to tell our replica where to get its data from. While inside the replica’s MySQL shell, run the following command to configure replication using the master’s details: CHANGE REPLICATION SOURCE TO SOURCE_HOST='mysql-master', SOURCE_USER='repl_user', SOURCE_PASSWORD='replication_pass', GET_SOURCE_PUBLIC_KEY=1; With the replication settings in place, let’s fire up the replica and get it syncing with the master. Still inside the MySQL shell on the replica, run: START REPLICA; This starts the replication process. To make sure everything is working, check the replica’s status with:
SHOW REPLICA STATUS\G; Look for Replica_IO_Running and Replica_SQL_Running — if both say Yes, congratulations! 🎉 Your replica is now successfully connected to the master and replicating data in real time.
Testing Our Replication Setup from the Node.js App Now that our replication is successfully set up, we can configure our Node.js server to observe the real-time effect of data being replicated from the master server to the replica server whenever we write to it. We start by installing the following dependencies:
npm i express mysql2 sequelize \ Now create a folder called src in the root directory and add the following files inside that folder connection.js, index.js and model.js. Our current directory should look like this We can now set up our connections to our master and replica server in the connection.js file as shown below
const Sequelize = require("sequelize"); const sequelize = new Sequelize({ dialect: "mysql", replication: { write: { host: "127.0.0.1", username: "root", password: "master", database: "replicaDb", }, read: [ { host: "127.0.0.1", username: "root", password: "slave", database: "replicaDb", port: 3307 }, { host: "127.0.0.1", username: "root", password: "slave", database: "replicaDb", port: 3308 }, { host: "127.0.0.1", username: "root", password: "slave", database: "replicaDb", port: 3309 }, ], }, }); async function connectdb() { try { await sequelize.authenticate(); } catch (error) { console.error("❌ unable to connect to the follower database", error); } } connectdb(); module.exports = { sequelize, }; \ We can now create a User table in the model.js file
const {DataTypes} = require("sequelize"); const { sequelize } = require("./connection"); const User = sequelize.define("User", { name: { type: DataTypes.STRING, allowNull: false, }, email: { type: DataTypes.STRING, unique: true, allowNull: false, }, }); module.exports = User \ and finally in our index.js file we can start our server and listen for connections on port 3000. from the code sample below, all inserts or updates will be routed by sequelize to the master server. while all read queries will be routed to the read replicas.
const express = require("express"); const { sequelize } = require("./connection"); const User = require("./model"); const app = express(); app.use(express.json()); async function main() { await sequelize.sync({ alter: true }); app.get("/", (req, res) => { res.status(200).json({ message: "first step to setting server up", }); }); app.post("/user", async (req, res) => { const { email, name } = req.body; let newUser = await User.build({ name, email, }); // This INSERT will go to the write (master) connection newUser = newUser.save({ returning: false }); res.status(201).json({ message: "User successfully created", }); }); app.get("/user", async (req, res) => { // This SELECT query will go to one of the read replicas const users = await User.findAll(); res.status(200).json(users); }); app.listen(3000, () => { console.log("server has connected"); }); } main(); When you make a POST request to the /users endpoint, take a moment to check both the master and replica servers to observe how data is replicated in real time. Right now, we are relying on Sequelize to automatically route requests, which works for development but isn’t robust enough for a production environment. In particular, if the master node goes down, Sequelize cannot automatically redirect requests to a newly elected leader. In the next part of this series, we’ll explore strategies to handle these challenges
