The technology was tricky, but the biggest hurdle was finding partners with different skill sets who would assemble all the pieces in just five months. It was an insane schedule, and we needed a partner who, besides meeting the technical requirements, would commit to the project and put in the resources to make it happen. This wasn’t an average networking job, but a visionary project to attempt something that had never been done before.
At this point, Riedel Networks stepped up. They had the technical capabilities for the project and felt it would be an excellent opportunity to showcase their strengths. I knew of Riedel and its stellar reputation from my racing background, and it was evident that they would be the right partner for the job.
Technical Difficulties and Environmental Complications
We had effectively three technological challenges to overcome. First, we needed the bandwidth to transmit the video and audio stream from the car to the simulator station. That data takes a lot of bandwidth. The second issue was latency. All signals have to be transmitted within a fraction of a second. At such high racing speeds, it’s dangerous to have a delay between the action on the track and the driver’s reaction in the simulator. It has to be as close to perfect real time as possible. Otherwise, the car can become uncontrollable. This concern leads to the third issue, which is the safety concern resulting from latency. The latency had to be extremely low throughout the entire drive. If it spiked above a certain threshold for only a moment, the car would have to stop automatically because we would have no way of knowing if the latency would persist.
Apart from the technical difficulties, we also faced complications around the environment of the test track, the Red Bull Ring in Spielberg, Austria. Spielberg is in the eastern part of the Alps, so we dealt with high altitudes and the valleys’ peaks, which are obstacles to radio signals. Red Bull Ring features a large steel bull in the center of the ring, and the radio network doesn’t like that, either. And then, we knew we’d have many other race teams there, each with their own radio networks, so we had to make sure our car was on a different frequency. As if all that wasn’t enough, we had to contend with a military airbase next door. Any time a fighter jet starts, the activation of those systems has the potential to disturb our radio network.
We also had to create a backup plan that ensured everyone’s safety in case of a network failure. In the worst-case scenario, we’d have a two-ton car traveling at 200 km/h with no one controlling it. It could be a disaster. So we had to think of Plan B should any component fail, from the power supply at the simulator station to the network itself to the drive-by-wire system. It was a lot to handle in a short time, and this is where the quality of our team mattered.
New Ideas and Last-Minute Changes
Schaeffler assumed the project lead role, assuming overall responsibility for the project, specifically for the car and drive-by-wire system. Riedel’s role was to plan the network coverage and secure the radio and data communication connections. We used a combination of two separate fiber-optic connections and 5G to ensure a stable connection between the simulator and car at all times.
When we first envisioned this project, the idea was to run the car remotely. But the further we got into the project, the conversation began to evolve yet again. We thought, “If we’re going to run the car remotely, why not run it from further away?” We decided to not just drive the car from a simulator placed in the pit lane, but to place the simulator 80 kilometers away, in Graz. But that meant we would have to transmit the signal even further, with the same reaction time. Our target was to transmit data from simulator to car and back to Graz in under a hundred milliseconds.
That’s when Riedel suggested a wide area network with two primary fiber-based connections plus a 5G backup. This raised the cost, but we didn’t have weeks to wait for a traditional evaluation process. Instead, Riedel Networks proposed that we speak with Cisco to sponsor this additional network. Cisco agreed, and finally, we had the network extension from Spielberg to Graz with a latency of less than 10 milliseconds from the race car to the simulator and back to the race car. For the remote driver, there was no difference between steering the car remotely at the pitlane or in the simulation center in Graz. The setup was perfect and made the showcase even more exciting.
Riedel was excellent throughout the project, both in the design of the network and as individual team members. As soon as we agreed on the administration and share of responsibilities, they placed people in our working group. At each of our weekly meetings, they always delivered. We came to rely on them for their expertise, efficiency, and reliability. It’s hard to find a team with such a high level of professionalism and motivation.
That’s not to say we didn’t run into issues. Even on the morning of the test, one of the mesh links failed, and the Riedel team had to get on the track, figure out what happened (the glass fiber connection had broken), access a locked room in a very crowded race day facility—all within 30 minutes. That’s what makes this team so special: we knew we would solve anything that came up. We made an excellent team, and we couldn’t have done this project in time without Riedel.
Making the Impossible Possible
As I stood by the side of the track, with the car passing two meters from me at 180 kph, after all those months of work, the reality of our accomplishment finally hit me. When you bring the right people together and let them do their thing, you can achieve extraordinary things—even in a short time.
Naysayers thought we couldn’t figure out how to run an electric car from a remote location in such a tight time frame, but we did more than figure out how to do it on paper. We did it on a real track, at a real race, with real people. On test day, I didn’t watch our car on a screen—I saw it with my own eyes.