Hi from Norway, I had all the problems that everyone in this forum is talking about, now on my
second car since "July" last year, the dealer and tech from MG in "Oslo" Norway burned my battery
on the first car from "July" trying to fix it after the main battery fuse blew-up on morning.
Got a new car in November 2020 (after 8 weeks waiting on a new MG on boat from China), now
with the famous BMS version from hell, then I got all the mentioned battery problems many of you
have seen, very poor follow-up from my dealer in the south of Norway, until the update in "January"
where it was upgraded, after that I was left to charge balance the car at home on granny.
After having the car for a few quick follow-up with the dealer the tech in their workshop said that
everything is back to normal, I did not think so after what I had seen from day to day then.
I bought an OBD2 plug to verify if this was true, I now have a problem to make the
"MG ZS - v1.2.1
- APP" run stable will connected to the OBD port.
The
"MG ZS - v1.2.1 - APP" is doing frequent crashes, then restarting, after that it's not running
stable anymore.
This is the OBD2 plug:
V1.5 OBD2 MINI - Android - Bluetooth
It's supporting the following protocol(s):
SAE J1850 PWM (41,6 Kbaud)
SAE J1850 VPW (10,4 Kbaud)
ISO 9141-2 (5 baud init, 10,4 Kbaud)
ISO14230-4 KWP (5 baud init, 10,4 Kbaud)
ISO14230-4 KWP (snabb init, 10,4 Kbaud)
ISO15765-4 CAN (11bit ID, 500 Kbaud)
ISO15765-4 CAN (29bit ID, 500 Kbaud)
ISO15765-4 CAN (11bit ID, 250 Kbaud)
ISO15765-4 CAN (29bit ID, 250 Kbaud)
The dealer of this OBD2 plug confirmed
"it supports the ATPPS instruction, and the PIC18F25K80
chip is also used"
Output from the "ELM327 Identifier:
Scan date=2021-04-10 19:06:00
Device name=OBDII
Device mac=00:1D:A5:06:EC:C0
Device Version (Declared)=ELM327 v1.5
Command Version Result RAW
ATPPFFON 1.1 OK ATPPFFON\r\nOK\r\n\r\n>
ATPPFFOFF 1.1 OK ATPPFFOFF\r\nOK\r\n\r\n>
ATPPS 1.1 OK ATPPS\r\n00:FF F 01:FF F 02:FF F 03:32 F\r\n04:01 F 05:FF F 06:F1 F
07:09 F\r\n08:FF F 09:00 F 0A:0A F 0B:FF F\r\n0C:68 F 0D:0D F 0E:9A F 0F:FF F\r\n10:0D F
11:00 F 12:FF F 13:32 F\r\n14:FF F 15:0A F 16:FF F 17:92 F\r\n18:00 F 19:28 F 1A:FF F 1B:FF
F\r\n1C:FF F 1D:FF F 1E:FF F 1F:FF F\r\n20:FF F 21:FF F 22:FF F 23:FF F\r\n24:00 F 25:00 F
26:00 F 27:FF F\r\n28:FF F 29:FF F 2A:38 F 2B:02 F\r\n2C:E0 F 2D:04 F 2E:80 F 2F:0A
F\r\n\r\n>
Anyone seen this problem using their own OBD2 plug in combination with the APP, I have tried this
using both of the following phones:
* Samsung Galaxy A3, SM-A310F, Android 7.0, / 3.10.61-13952378
* Samsung Galaxy A21s, SM-A217F/DSN, Android 10 / 4.19.132-20058569
Sorry for this long posting, very good forum and many excellent contribution(s), hope to be part of
sharing some knowledge in the coming future with my car from Norway.