Toyota: Car location data and videos of 2M customers exposed for ten years

I worked for Toyota Infotechnology Center in Sunnyvale in 2016/2017 on a robotics research project involving their HSR robot running ROS.

The robot had odometry from the wheels, though it was a bit noisy due to the construction of the omnidirectional mechanism. They decided to ignore wheel odometry and use only an odometry module based on the planar lidar, essentially visual odometry. This worked fine in most circumstances, but basically completely failed in hallways as they lacked distinctive features. This interfered with my work which involved the robot navigating around the office.

I had worked on this problem before, and ROS has an excellent sensor fusion library for dealing with multiple noisy sensor readings. You just need to combine wheel odometry and laser odometry with a kalmann filter, and the sensor fusion library makes this relatively easy.

However even though I worked at a Toyota office with full time Toyota employees, and the code was pretty much off the shelf ROS code, and the robots were produced in very low volumes and only in use at Toyota, they wouldn't give me the source code. I think maybe they wouldn't even give me root access.

Still, I was able to control the names of ROS topics using the ROS launch files (it has been a while since I worked with ROS and I forget some of the terms). I remapped the lidar odometry topic to an intermediary topic name instead of /odom, then directed the intermediary topic in to the sensor fusion module along with the wheel odometry, then mapped the sensor fusion output to /odom. The system got odometry information but now it did not come from the lidar odometry but from the sensor fusion module, so it was happy.

The fix worked great. It had normal behavior when lidar was good, and had reliable odometry in long hallways. I was finally able to implement my office navigation code.

I did my best to communicate these changes back to Toyota. They had not been very helpful when I was asking for help solving the issue, but I had hoped that since I had it working they would appreciate this. I asked where I could file a git issue or otherwise push the code to some private git repo.

They were not using git. Ultimately I was instructed to email the raw code files I had used along with instructions for how to integrate it. I found this quite surprising. I have no idea if they ever implemented the changes I suggested, but I kind of doubt it. From what I have heard of japanese software practices, they basically do not accept code suggestions from the bottom up.

I know of some people who worked for Toyota Research Institute who said they were trying to get the Toyota folks to integrate silicon valley coding rigor in to their systems. Maybe they had success, I don't know. But certainly 6 years ago things were a total mess.

japan is a US protectorate. when china starts marketing their EV's abroad the US will just sanction them. don't worry, japan is safe.

Japan generally. They tried to pull a great leap forward move with AI a few decades ago, but just ended up wasting billions on dead end approaches right on the cusp of the AI winter. My personal opinion is that really top notch breakthrough software engineering and computer science is susceptible to an exponential cascade butterfly effect.

Yes you need big teams to deliver huge projects. Operating systems, compilers, languages, etc all take huge investment to build out. The thing is though the initial conditions have a massive downstream effect. The core contributions by genius 10x computer scientists and software engineers set the pace for everyone else. Unix, C, Linux, Git, LLVM, Perl, Python, who knows what else. It's the individuals or small dedicated teams doing it the 'wrong' way, or going for a weird untested approach that starts a small speck that snowballs into huge multi-billion industries.

The culture and economic conditions in the US are perfect for this to work. Japan, and for different reasons and certainly not the the same scale Europe, not so much.

> silicon valley coding rigor

This was refreshing to read. Within my bubble in tech, it's often easy to get jaded about how _unrigorous_ our "engineering" often is.

I hope regulators fine the hell out of these companies. Enough to make them think twice about offering these upload everything to the cloud services no one really asks for.