Advertisement
Australia markets closed
  • ALL ORDS

    7,817.40
    -81.50 (-1.03%)
     
  • ASX 200

    7,567.30
    -74.80 (-0.98%)
     
  • AUD/USD

    0.6423
    -0.0002 (-0.03%)
     
  • OIL

    83.05
    +0.32 (+0.39%)
     
  • GOLD

    2,409.30
    +11.30 (+0.47%)
     
  • Bitcoin AUD

    100,468.15
    +1,643.73 (+1.66%)
     
  • CMC Crypto 200

    1,388.26
    +75.64 (+6.12%)
     
  • AUD/EUR

    0.6025
    -0.0006 (-0.09%)
     
  • AUD/NZD

    1.0897
    +0.0022 (+0.20%)
     
  • NZX 50

    11,796.21
    -39.83 (-0.34%)
     
  • NASDAQ

    17,125.00
    -269.32 (-1.55%)
     
  • FTSE

    7,895.85
    +18.80 (+0.24%)
     
  • Dow Jones

    37,922.74
    +147.36 (+0.39%)
     
  • DAX

    17,737.36
    -100.04 (-0.56%)
     
  • Hang Seng

    16,224.14
    -161.73 (-0.99%)
     
  • NIKKEI 225

    37,068.35
    -1,011.35 (-2.66%)
     

Roborace engineer explains why a driverless racecar drove into a wall

The SIT Acronis Autonomous car was doomed before the start of its fateful lap.

Acronis SIT Autonomous

A video of an unfortunate (albeit kinda hilarious) Roborace incident made the rounds on Thursday. It showed an SIT Acronis Autonomous racecar immediately veering to the right at the start of a lap and crashing into a wall. An engineer from SIT has since taken to Reddit to explain how the embarrassing incident happened during the Season Beta 1.1 race.

They wrote that a problem emerged during the initialization lap, in which a human driver takes the car to the start line. An error occurred which caused the steering to lock all the way to the right.

"When our car was given [permission] to drive, the acceleration command went as normal but the steering was locked to the right," the engineer wrote. "We are looking at the log values and can see that our controller was trying to steer the car back to the left, but the car did not execute the steering command due to a steering lock. The desired trajectory was also good; the car definitely did not plan to go into the wall."

The engineer suggested it was "an extremely rare event during which there was a short spike in the inputs to the controller." Although SIT has made some fixes in an attempt to mitigate the issue, it had to send the car back to the factory for repairs. As such, it ran the race's second round using a default Roborace car.