this post was submitted on 27 Nov 2023
69 points (98.6% liked)
[Dormant] Electric Vehicles
3206 readers
2 users here now
We have moved to:
A community for the sharing of links, news, and discussion related to Electric Vehicles.
Rules
- No bigotry - including racism, sexism, ableism, casteism, speciesism, homophobia, transphobia, or xenophobia.
- Be respectful, especially when disagreeing. Everyone should feel welcome here.
- No self-promotion.
- No irrelevant content. All posts must be relevant and related to plug-in electric vehicles — BEVs or PHEVs.
- No trolling.
- Policy, not politics. Submissions and comments about effective policymaking are allowed and encouraged in the community, however conversations and submissions about parties, politicians, and those devolving into general tribalism will be removed.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Mine does, do others actually not?
I plugged a Bluetooth OBD II Sensor into my car and downloaded an app, it lets me see all of the detailed info on my car. The coolest info is seeing the battery voltage and resistances between cells and shit
When my battery melted I was able to show the tech exactly which cells had failed, he took 2 mins to check and came back with "yup it was those 3"
OBD2 is federally required for all cars sold in the US. That doesn’t mean it has to be useful though, it just has to say if there’s any emissions failures really which don’t apply to EVs.
The OBDII standard requires a standardized port with a standardized network using a standardized language, and what data must be available to monitor.
So every car with OBDII has all engine control or emissions related data available. What is not required to be standardized on an OBDII system are non-emissions related data, like what the climate control module is saying.
It is not just a way to get the standardized code for a check engine light, you can also see the data for that code like the sensor reading and sensor voltage.
The rest of the data on the canbus should be required to be disclosed publicly by manufacturers, instead of needing homebrew or 3rd party deciphering to understand all the data that is on the network.
As someone who's shop has 5 different scanners, several different laptops for all the different modules on heavy trucks, and has worked on hybrids... it's a bit absurd how expensive it is to even know what a computer is trying to tell you.
Your can read most codes with a generic scanner. Anything past that, like trying to see the oil pressure will be available on some scanners. The only way to see everything, set everything, program everything, the most guaranteed way is with a proprietary scanner.
Which I'm sure the main reason why they do this is to have fewer people able to work on their own car, so they can make more money. John Deere is definitely a pioneer in this business strategy. Working on them "correctly" is like pulling teeth if you're not a dealer.
Heavy trucks and farm equipment OEMs are dicks. For most cars an Autel can do a lot of heavy lifting until you get into module reprogramming. Something like Oil pressure isn't on the OBDII standard for some dumb reason.
I wish that they made it a law that any canbus data has to have the key released into the publoc domain so any scantool can give that data. They can keep their specific module reprogramming hardware and software access subscriptions, but the data in the network should be available.
Yours has the tech, but others may not. Would be great to have this standardized by the time EV manufacturers adopt NACS.
This is good info: what EV?
My Nissan Leaf has excellent OBD support.