Aiways - Mode 22 and PID's

Telematics Question
1

Hello,

I am currently working with the FMC003 device and exploring its capabilities for advanced vehicle diagnostics via OBD-II.

My use case involves accessing manufacturer-specific data from Aiways vehicles, using Mode 22 (extended diagnostics PIDs).

We already have confirmed working PIDs, as we successfully retrieve this data using other diagnostic tools and scanners. These tools allow us to query Mode 22 and obtain extended parameters beyond standard OBD-II (Mode 01).

Our goal is to replicate this functionality using the FMC003, specifically to:

  • Send Mode 22 requests

  • Configure and use custom PIDs

  • Parse the responses and forward the data through AVL records

This is particularly important for retrieving advanced vehicle data such as:

  • Detailed battery info and metrics

  • Manufacturer-specific engine parameters

  • Additional sensor data not available via standard PIDs

At the moment, I could not find clear documentation or configuration options for:

  • Sending Mode 22 requests

  • Defining custom PIDs (including CAN header, service, PID, and response parsing)

  • Mapping this data into AVL records

Could you please clarify:

  1. Does FMC003 support Mode 22 requests?

  2. Is it possible to define and use custom PIDs manually?

  3. Are there any workarounds or undocumented features for this?

  4. If not currently supported, are there plans to include this in future firmware updates?

This capability would be extremely valuable for advanced telematics use cases and integration with OEM-specific vehicle data.

Thank you in advance for your support.

Best regards,

2

Good Day,

Regarding your inquiry, the FMC003 does not currently support manual Mode 22 (extended diagnostics) requests or user-defined custom OBD-II PIDs. The device reads vehicle data using the internally supported PID database and automatic detection logic, and there is no configuration option available to manually define CAN headers, diagnostic services (such as Mode 22), or custom PID parsing rules. Because of this, manufacturer-specific parameters (such as advanced EV battery metrics or proprietary sensor data) can only be obtained if they are already included in the supported vehicle/OEM parameter list.

Best Regards,

Imran S.

3

ive JUST bought this device to something similar, seems its no good to me now

Do i need this to get back hybrid battery SOC?

4

Hello,

I would like to submit a detailed and technical request regarding support for Aiways vehicles (U5) in Teltonika OBD devices such as FMC003.

Important context

Aiways has discontinued its official connected services platform, which means that vehicle owners and fleet operators currently have no way to monitor key EV data such as battery state of charge (SoC).

Because of this, integrating Aiways support into Teltonika devices would provide a critical solution for all existing Aiways customers, enabling:

  • Real-time battery monitoring

  • Charging status tracking

  • Fleet management capabilities

Technical validation (working data)

We have already successfully validated communication with the vehicle using external diagnostic tools.

Protocol:

  • ISO 15765-4 CAN (11-bit ID, 500 kbps)

Initialization commands:
ATZ
ATD0
ATE0
ATSP6
ATM0
ATS0
ATAL
ATAT1
ATST64
ATSH703

Service:

  • Mode 22 (extended diagnostics)

Verified working data (Mode 22)

Below is a subset of confirmed working PIDs and their decoding formulas:

  • 221006 → State of Charge (SoC)
    Equation: A

  • 221012 → State of Health (SoH)
    Equation: A

  • 221005 → Battery Current
    Equation: (((signed(A)*256)+B)-7000)/10

  • 221004 → Battery Voltage
    Equation: ((signed(A)*256)+B)/10

  • 221002 → Battery Temperature
    Equation: A-40

  • 221009 → State of Energy (SoE)
    Equation: A*6.3

  • 221202 → Vehicle Speed
    Equation: ((A*256)+B)/100

  • 22DF05 → Odometer
    Equation: (A65536+B256+C)/10

Additional working requests:
221000, 221001, 221002, 221004, 221005, 221006, 221009, 221010, 221202, 221012, 22DF05

All these parameters return stable and valid data when tested with standard diagnostic tools.

Project goal

  • Read EV data from Aiways vehicles using FMC003

  • Send AVL data to Flespi

  • Enable real-time monitoring of EV metrics (SoC, battery health, energy, etc.)

Request

Given that this data is already validated and available from the vehicle, we would like to ask:

  1. Is it possible to add Aiways (U5) to the supported vehicle list using this information?

  2. What is the process to submit a complete PID set for internal validation?

  3. Would your team be open to collaboration to accelerate implementation?

We are available to provide:

  • Full PID list

  • Raw CAN logs

  • Additional testing

  • Real vehicle access if required

This would not only support our project, but also provide a valuable solution for all Aiways users, who currently lack any official way to monitor their vehicles.

Thank you very much for your time and consideration.

Best regards,