Cars Forum

Thanks Jeff! Let me
Know if you need anything! Sleep well!

First few steps in place for handling extended addressing!

First up, the Command JSON specification has been updated to include support for specifying eax (extended address) values for commands: https://sidecar.clutch.engineering/scan ... s/#command. This will allow us to more accurately target specific ECUs for specific commands. There's an open question here of whether we need this extended addressing for the service 01 commands though, so @Tombmwi3 if I can get you to do one more test run in your Terminal this would be super helpful:

ATCEA07
0100
0902
010D
ATFCSH7DF
ATFCSD07300800
ATFCSM1
0100
0902
010D
ATFCSH7DF
ATFCSD07300000
ATFCSM1
0100
0902
010D

Second up, I've updated the CAN frame scanner logic to handle extended addressing modes, and this functionality will go out in the next release of the CANDecoder app:

I've gotten a bunch of potential parameters wired up for the i3 in the v1.19.1 TestFlight build:

• Odometer
• Speed
• Range
• SoC
• SoH

Full specs: https://github.com/OBDb/BMW-i3/blob/mai ... fault.json

This is great! I’ve sent over my logs.

@Tombmwi3 do you have access to an i3S too?

Vehicle symbol

Whooo! i3 is officially onboarded We can still use additional testing on other model years but I'll be graduating this car out to the onboarded vehicles forum now

I do have access to an i3S I’ll get some logs.

Also this should theoretically work with the mini electric as it uses i3 components.

@Tombmwi3 let's start a separate thread for the i3S once you're able to test with it!