• Zwuzelmaus@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 hours ago

    but integrating that is hard

    No harder than all the other points where Waymo IT needs to talk with car IT.

    • greyscale@lemmy.grey.ooo
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      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.

      • Zwuzelmaus@feddit.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 hours ago

        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.

        • greyscale@lemmy.grey.ooo
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 hours ago

          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.