Simplifying the Driverless Truck
Engineers and innovators continue the push towards implementation of driverless vehicles into various sectors of the market. Launching driverless vehicles means, in part, overcoming the obstacles that hinder progress, such as driving in crowded, urban areas or bad weather. One of the sectors hoping to overcome such obstacles quickly is the trucking sector. Developers in this area seek to simplify the role and usage of driverless trucks to avoid as many unforeseen problems as possible while simultaneously implementing the technology into the market more quickly.
For example, TuSimple – a company that develops automated trucking systems – may first deploy driverless trucks that stay on open roads and highways and avoid crowded cities since driving in crowded areas involves different and more complex technology. Another example is deploying driverless trucks solely in good weather for the same reason: navigating harsh weather requires different and more complex technology. By skimming down the functions and responsibilities of driverless trucks, TuSimple can get them on the road sooner.
Another way to introduce driverless trucks to the market sooner is by using a strategy known as “autonomous convoying.” This is where an actual driver operates one truck while a driverless truck follows. The logic behind this approach is that the driverless truck – while depending on its automated systems – can follow the experienced driver ahead, thereby reducing potential problems and issues for the driverless truck. For example, a human driver can read the construction signs ahead of time and know to slow down in advance. The benefits work the other way around as well: when the driver needs to sleep, he or she can have the driverless truck takeover while they sleep without having to pull over and stop.
The bottom line: driverless truck developers hope to see the technology implemented into the trucking sector sooner rather than later. Simplifying the functions and roles of driverless trucks can help overcome obstacles and jump-start implementation.
Taken from: www.sae.org