Probably a design issue where they couldn’t hook into one of the car’s systems? I’m not sure.
Their current cars are just temporary anyways. Jaguar doesn’t even make them any more - they stopped producing the model that Waymo uses at the end of 2024.
You’d think so… buuuut… sometimes the people problem is greater than the technical ones.
I can foresee the trunk release talking to a controller with one-time-programmable ROM. I can see the trunk release button being activated or deactivated by messages from the body control module. I can imagine the controller reporting trunk open/closed based on its latch, but not having a way to report to the BCM if the button was -pushed- rather than the lock/latch actuated.
But all of this is already decided and designed and built in the car IT. The trunk is really nothing special, it is actually one of the simplest controllers in a car.
Yes. Which is why it will be cost-optimised to hell. And could conceivably not have a way to tell you the button state vs whether or not it should/shouldn’t open. One requires bi-directional communication. And to change the behaviour of something that cost-optimised will require a different mask rom, possibly. Or they just can’t be bothered to make a separate SKU just for Waymo for a lifetime-limited rental car product.
Sometimes something very simple has a bunch of stupid structural reasons it can’t be done without spending real money.
Probably a design issue where they couldn’t hook into one of the car’s systems? I’m not sure.
Their current cars are just temporary anyways. Jaguar doesn’t even make them any more - they stopped producing the model that Waymo uses at the end of 2024.
They’re currently partnering with Zeekr to build a brand new one. https://en.wikipedia.org/wiki/Waymo_Ojai
If they can literally steer and accelerate the car with a computer, they could surely detect if a door or latch was opened at any point.
Hobbyists have been doing it for cheap using home assistant and cheap sensors, I’m sure a company valued at 100+ Billion could too.
That’s what I thought too. I’m not sure why it’s not the case.
They could have run a whole ass extra wire to the trunk release button input if they wanted to, they just didn’t want to.
But I like how friend-shaped that Zeekr is.
Hell, my wife’s entirely manual Jeep (manual door locks, manual window cranks, etc.) still has a sensor that warns you if the tailgate is open…
LOL extra wire.
They already should have a normal controller there… button state, lock state, lid angle, a motor if it’s the luxury config…
Well yes, but integrating that is hard and would require talking to Jaguar. Waymo could have pulled a single wire if they wanted to.
No harder than all the other points where Waymo IT needs to talk with car IT.
You’d think so… buuuut… sometimes the people problem is greater than the technical ones.
I can foresee the trunk release talking to a controller with one-time-programmable ROM. I can see the trunk release button being activated or deactivated by messages from the body control module. I can imagine the controller reporting trunk open/closed based on its latch, but not having a way to report to the BCM if the button was -pushed- rather than the lock/latch actuated.
But all of this is already decided and designed and built in the car IT. The trunk is really nothing special, it is actually one of the simplest controllers in a car.
Yes. Which is why it will be cost-optimised to hell. And could conceivably not have a way to tell you the button state vs whether or not it should/shouldn’t open. One requires bi-directional communication. And to change the behaviour of something that cost-optimised will require a different mask rom, possibly. Or they just can’t be bothered to make a separate SKU just for Waymo for a lifetime-limited rental car product.
Sometimes something very simple has a bunch of stupid structural reasons it can’t be done without spending real money.