Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 8:41 pm
Thank you! Looking now.
Cars Forum
The community for drivers, technicians, owners, buyers, and enthusiasts
https://meta.cars.forum/
✅ BMW X3 M40i support
Page 2 of 4
Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 9:23 pm
What do you get when you run the command you found on the other forum?
Code: Select all
ATSH300
22F190Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 9:30 pm
I've merged in 22F190 as the ODO pid in SHA: c53680d if you want to give that a try.
Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 9:48 pm
Still no data. Tried above command too and no data
Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 9:54 pm
Oh wait
Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 9:57 pm
Sent you the log. 01A6 in the terminal works but doesn’t show up under connectables. Good news is that 01A6 works 
Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 10:00 pm
012F works in a new terminal as well. Battery voltage now shows up under connectables.
Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 10:43 pm
So in your logs it looks like the parameter support handshake in the most recent session is only returning parameters from ECU 7E1.
In the most recent session that you sent via email, was your car ignition off when you started the scan session?
Scan session where your car returned its VIN right away
Code: Select all
> ATZ ATZ
ELM327 v2.2
> ATPPS ATPPS
00:FF F 01:FF F 02:FF F 03:32 F
04:01 F 05:FF F 06:F1 F 07:09 F
08:FF F 09:00 F 0A:0A F 0B:FF F
0C:68 F 0D:0D F 0E:FA F 0F:D5 F
10:0D F 11:00 F 12:FF F 13:55 F
14:50 F 15:0A F 16:FF F 17:92 F
18:31 F 19:4F F 1A:0A F 1B:0A F
1C:03 F 1D:0F F 1E:4A F 1F:FF F
20:03 F 21:FF F 22:62 F 23:00 F
24:00 F 25:00 F 26:00 F 27:FF F
28:FF F 29:FF F 2A:3C F 2B:02 F
2C:E0 F 2D:04 F 2E:80 F 2F:0A F
30:42 F 31:01 F 32:F0 F 33:06 F
34:E0 F 35:0F F 36:FF F 37:FF F
> ATWS ATWS
ELM327 v2.2
> ATE0 ATE0
OK
> ATM0 OK
> ATS0 OK
> ATAT1 OK
> ATH1 OK
> ATSP6 OK
> ATS0 OK
> ATDPN 6
> 0902 7E8....valid
> 0100 7E8064100BE3EA813
7E906410098188001
7EF06410098188001
> 0120 7E8064120A007B011
7E906412080000001
7EF06412080000001
> 0140 7E8064140FED08411
7E9064140C0000000
7EF064140C0000000
> 0180 7E80641800004000D
> 01A0 7E80641A004000000Scan session that did not return a VIN right away
Code: Select all
> ATZ
ELM327 v2.2
> ATPPS ATPPS
00:FF F 01:FF F 02:FF F 03:32 F
04:01 F 05:FF F 06:F1 F 07:09 F
08:FF F 09:00 F 0A:0A F 0B:FF F
0C:68 F 0D:0D F 0E:FA F 0F:D5 F
10:0D F 11:00 F 12:FF F 13:55 F
14:50 F 15:0A F 16:FF F 17:92 F
18:31 F 19:4F F 1A:0A F 1B:0A F
1C:03 F 1D:0F F 1E:4A F 1F:FF F
20:03 F 21:FF F 22:62 F 23:00 F
24:00 F 25:00 F 26:00 F 27:FF F
28:FF F 29:FF F 2A:3C F 2B:02 F
2C:E0 F 2D:04 F 2E:80 F 2F:0A F
30:42 F 31:01 F 32:F0 F 33:06 F
34:E0 F 35:0F F 36:FF F 37:FF F
> ATWS ATWS
ELM327 v2.2
> ATE0 ATE0
OK
> ATM0 OK
> ATS0 OK
> ATAT1 OK
> ATH1 OK
> ATSP6 OK
> ATS0 OK
> ATDPN 6
> 0902 NO DATA
> 0902 NO DATA
> ATSH7E0 OK
> 0902 NO DATA
> 0902 NO DATA
> ATWS
ELM327 v2.2
> ATE0 ATE0
OK
> ATM0 OK
> ATS0 OK
> ATAT1 OK
> ATH1 OK
> ATSP7 OK
> ATS0 OK
> ATDPN 7
> 0902 NO DATA
> 0902 NO DATA
> 0902 NO DATA
> 0902 NO DATA
> ATSP6 OK
> ATWS
ELM327 v2.2
> ATE0 ATE0
OK
> ATM0 OK
> ATS0 OK
> ATAT1 OK
> ATH1 OK
> ATSP6 OK
> ATS0 OK
> ATDPN 6
> 0100 7E906410098188001
> 0120 7E906412080000001
> 0140 7E9064140C0000000Re: BMW X3 M40i support
Posted: Fri Oct 04, 2024 10:43 pm
One thing to test: make sure your ignition is on before connecting Sidecar to your scanner. Do you see your odometer parameter in this case?
Re: BMW X3 M40i support
Posted: Sat Oct 05, 2024 1:59 am
So from what I can see in the logs, it looks like 01A6 is only returning values when the header/receive masks aren't set. So let's try a few more approaches:
No masking, new terminal session
This worked for you before, but let's confirm it's still working.
Code: Select all
01A6New terminal session, just receive filtering
This should still work, because we're only filtering on the known receive address (7E8)
Code: Select all
ATCRA7E8
01A6New terminal session, header + receive filtering
The first one should not work:
Code: Select all
ATSH7E0
ATCRA7E8
01A6If the first two work and the third doesn't, then the BMW is not following the standard +8 offset practice and a different ECU needs to be targeted in order to speak to the Odometer. We can try brute forcing ECUs to see which one will talk to us:
New terminal session, brute force (copy all of these and paste at once to send it as a block)
Code: Select all
ATSH7E0
01A6
ATSH7E1
01A6
ATSH7E2
01A6
ATSH7E3
01A6
ATSH7E4
01A6
ATSH7E5
01A6
ATSH7E6
01A6
ATSH7E7
01A6