Why don’t EVs have standard diagnostic ports—and when will that change? | OBD-II was implemented to monitor emissions, but EVs don’t have tailpipes.::OBD-II was implemented to monitor emissions, but EVs don’t have tailpipes.

  • 0ops@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I think it’s worth noting that the obd-2 protocol required by law is ONLY for emissions related parameters. Knock, air/fuel ratio, throttle position, things like that. A lot of manufacturers can get data that’s not emissions related (like transmission codes) from the obd-2 port, but with a different/extended proprietary protocol that requires a proprietary (very expensive) scanner.

    Basically, I think obd-2 should be expanded to include these other systems and ev systems as well. That would standardize ev diagnostics and non-emissions-related ice diagnostics too, which would be a boon for repairability.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    This is the best summary I could come up with:


    But most call an ALDL the OBD-II port because it provides everyone from engineers at proving grounds to dealership technicians to shade tree mechanics a connection to the vehicle’s software and diagnostic systems.

    Modern onboard diagnostics, or OBD-II, became a standardized and mandatory part of every automobile sold in the United States, starting with the 1996 model year.

    The ALDL port originated from General Motors in the early 1980s in its pursuit to produce systems and diagnostics for its cars to meet new government emissions regulations.

    By the late '80s, the California Air Resources Board (CARB) got involved and mandated that all 1991 model-year or newer cars sold there must include an onboard diagnostics system to manage and control emissions.

    But as EVs become more mainstream, they include a variety of sensors and systems to keep everything running optimally, oftentimes more than any internal combustion engine-powered vehicles.

    Part of California’s sweeping set of rules for cars sold in the state requires EVs, hydrogen fuel cells, and Plug-in Hybrids to follow a similar diagnostics standard, much like OBD-II did 30 years earlier.


    The original article contains 839 words, the summary contains 181 words. Saved 78%. I’m a bot and I’m open source!

  • Overspark@feddit.nl
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    My i3 has an OBD-II port, and it’s not the only EV that has one. Bimmercode can change A LOT of vehicle settings through the port, and software like ABRP can use it to read out the battery level and route you to the next charger when needed.

    • Kecessa@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 year ago

      I’m surprised more people don’t realize that OBDII is basically “car USB” at this point… Info can go both ways and a lot more info comes out of the car than it did in 95 when it was introduced AND we’re able to reprogram cars using it!

  • Gormadt@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I just assumed they had an OBD-II port

    Honestly it’s such a stupid idea to not have a standard diagnostic port in there especially considering the standard has already existed for over 20 years

      • brianorca@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Established manufacturers could technically ditch the port on EV models, but they don’t because they have other models which are still ICE, so they need it there. Many of the modules are shared between models, so they use the same bus when it’s ICE, hybrid, or EV.

        • Kecessa@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          And they already have their tools in the hands of their mechanics that they just need to update OTA so they’re compatible with their EV cars… Even if gas cars stopped existing, replacing all of that would be too much of a pain to change the plug…

    • zurohki@aussie.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      My BYD Atto 3 does. It’ll tell me battery cell voltages, highest cell voltage, lowest cell voltage, highest cell temperature, lowest cell temperature, maximum power, overall pack voltage, pack current, 12V battery voltage.

      There’s a fair bit of data there.

    • redhydride@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      It is. But also it makes ev owners crawl back to the dealer or manufactures to get their car fixed

      • Gormadt@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Yeah from a repairability stand point that’s probably a key factor

        “If we have our own plug and our own protocol then that means they have to use our tool, and if we don’t license the software or sell the tool then they have to come back and pay our prices.”

  • tankplanker@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    The existing standards OBD-II and CAN Bus just aren’t fit for purpose for ICE cars let alone EVs. Too many keyless cars get hacked by the thief hacking into either system and overriding the lack of a key, even if it means cutting a hole in the boot lid to expose the CAN Bus connection as with some Range Rovers.

    Its become a significant problem for a lot of cars. It used to be that they would break into your house to steal your key, then steal the car but now they do not need to do that. It can be done in a couple of minutes on some cars that do not properly protect the CAN Bus cable.

    What we really need is a proper public/private key pair for the cars so that all comms is only authorised via the physical key fob. This needs to be touch authorised to prevent snoop attacks. Sticking it on the key would then mean right to repair is not blocked, if the main dealer has it then its a big blocker for right to repair.

    • frezik@midwest.social
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 year ago

      It’s not that simple. The CAN bus isn’t just about unlocking doors and rolling down windows. It also controls airbags and other systems that are time-sensitive. If you’re rolling down the window at the same time you get in a crash, the airbag message has to override the window rolling message and inflate those bags in right-the-fuck-now time.

      Adding encryption to the mix greatly increases the engineering required, even if it’s not used for every kind of message.

      • tankplanker@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Yes I am aware of that, however the current way that is being looked at addressing the problem is moving the cabling to further within the car, which is just pathetic, like thieves wont just adapt to that.

        Encryption really isnt as big a performance impact if it is done correctly, sure it is not cost neutral but ask Range Rover how much reputational damage they had with their piss poor security. They are still having 1 in a 300 brand new defenders stolen after adding what is pretty a traditional immobiliser and tracker.

        As an example: https://iopscience.iop.org/article/10.1088/1742-6596/2006/1/012071

        • frezik@midwest.social
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Encryption really isnt as big a performance impact if it is done correctly

          “Done correctly” is the trick. This takes careful analysis and design. You don’t just pour on encryption and hope everything will be fine.