Cannot read Kona EV custom PIDS

[tavius]

Hello:
This is driving me crazy. I'have tried all can procotols to retrieve custom PID 220101 and 220105 from Hyundai kona (header 7E4) and I don't receive nothing. In auto it said unable to connect.

Code: Select all

char *SendObdCommand(char *msg, unsigned int timeout)
{
  static char command[32], buffer[1024];
  sprintf(command, "%s\r", msg);
  Serial.println(command);
  obd.link->sendCommand(command, buffer, sizeof(buffer), timeout);
  for (int f = 0; f < strlen(buffer); f++)
    if (buffer[f] == '\r')
      buffer[f] = '\n';
  Serial.println(buffer);
  delay(1000);
  return (buffer);
}
void setup()
{
  char buffer[128];
  if (sys.begin())
  {
    pinMode(PIN_LED, OUTPUT);
    digitalWrite(PIN_LED, HIGH);
    delay(1000);
    digitalWrite(PIN_LED, LOW);
    Serial.begin(115200);
    Serial.print("TYPE:");
    Serial.println(sys.devType);
    Serial.println("Calling obd.begin");

    obd.begin(sys.link);

    for (int f = 3; f < 10; f++)
    {
      SendObdCommand((char *)"ATZ", OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"ATE0", OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"ATL0", OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"ATS0", OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"ATH1", OBD_TIMEOUT_SHORT);
      sprintf(buffer,"ATSP%X",f);
      SendObdCommand((char *)buffer, OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"ATSH7E4", OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"220101", OBD_TIMEOUT_LONG);
      SendObdCommand((char *)"ATSH7E4", OBD_TIMEOUT_SHORT);
      SendObdCommand((char *)"220105", OBD_TIMEOUT_LONG);
    }
  }
}

This is the output....

Code: Select all

ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP3
OK

>
ATSH7E4
ERROR

>
220101
BUS
INIT:
...ERROR

>
ATSH7E4
ERROR

>
220105
BUS
INIT:
...ERROR

>
ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP4
OK

>
ATSH7E4
OK

>
220101
BUS
INIT:
...ERROR

>
ATSH7E4
OK

>
220105
BUS
INIT:
...ERROR

>
ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP5
OK

>
ATSH7E4
OK

>
220101
BUS
INIT:
...ERROR

>
ATSH7E4
OK

>
220105
BUS
INIT:
...ERROR

>
ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP6
OK

>
ATSH7E4
OK

>
220101
NO DATA

>
ATSH7E4
OK

>
220105
NO DATA

>
ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP7
OK

>
ATSH7E4
OK

>
220101
NO DATA

>
ATSH7E4
OK

>
220105
NO DATA

>
ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP8
OK

>
ATSH7E4
OK

>
220101
NO DATA

>
ATSH7E4
OK

>
220105
NO DATA

>
ATZ
ELM327 v1.5

>
ATE0
OK

>
ATL0
OK

>
ATS0
OK

>
ATH1
OK

>
ATSP9
OK

>
ATSH7E4
OK

>
220101
NO DATA

>
ATSH7E4
OK

>
220105
NO DATA

>

Does anybody know the correct way to retrieve customs pids with freematics+ model H. I'm starting to think this interfaces is useless for me

Thanks in advance.
Octavio.

[stanley]

Only standard OBD PIDs are supported. Custom PIDs are not guaranteed to work. You can try CAN sniffing though.

[tavius]

I do not understand. With other ELM327 OBD interfaces I can query this customs PIDS. Where is the limitation? In the chips used in freematics? The firmware?.

Thanks.
Octavio.

[Deferral7391]

I followed along with my Freematics ONE+ Model B and Kia EV6 (same platform as Hyundai Ioniq 5) and was able to read 220101 and 220105:

Code: Select all

AT@1
OBDII to USART Interpreter

>ATZ
ELM327 v1.5

>ATE0
OK

>ATH0
OK

>ATSP6
OK

>ATSH 7E4
OK

>ATMA
?

>ATCFC1
OK

>ATCM7FF
OK

>ATCF7EC
OK

>220101
03E 0: 62 01 01 EF FB E7 
1: EF 6D 00 00 00 00 00 
2: 00 09 1C 14 13 12 13 
3: 13 12 12 12 00 3C BB 
4: 27 BB 08 00 00 87 00 
5: 00 06 DC 00 00 06 F1 
6: 00 00 05 29 00 00 05 
7: 11 00 08 EB 52 00 02 
8: CE 00 00 00 00 06 B0

>220105
02E 0: 62 01 05 FF FB 74 
1: 0F 01 2C 01 01 2C 12 
2: 12 12 12 12 12 12 6C 
3: 34 6C 34 00 00 50 14 
4: 00 03 E8 00 49 A4 00 
5: 6C 00 00 00 00 00 00 
6: 00 12 12 13 12 00 00 

No clue how to interpret this yet but looks like it's possible to talk to EVs.

[ankostis]

Interesting, thanks!

How did you send the AT-commands?