OBD II UDS SCRIPT

Open

Script Description

OBD II UDS script is made for XtCAN devices. Script is plug and play, device just needs to be plugged into OBD II socket, configured and it will start sending telemetry data.

OBD II script is capable of:

• Reading Diagnostic Trouble Codes (DTCs) and presenting in P, U, C, B codes. More information about DTC codes here.

• Reading vehicle parameters. Parameters are read using service 01 defined by SAE J1979 standard. Not all vehicles will support all PIDs.

• Reading manufacturer specific data. Fuel level, mileage, state of charge (for hybrid (HV) or electric vehicles (EV)), driver belt status, passenger belt status.

Configuration

• General settings

• Service 01 settings

• Queries settings

• DTCs settings

Script already tested on

Link to vehicles tested.

NOTE: OBD II Service 1 pids, DTC codes and VIN reading should work on ALL VEHICLES, even if they are not in the list linked above.

Troubleshooting

First step of troubleshooting is to always check if physical connection is good, wires/connector is not loose.

Events list to help troubleshooting occurring problems.

Connection

If you are using OBD II cable bought from us, simply connect it to OBD II socket in vehicle. Usually OBD II socket is in one of the places marked below. If you cannot find it check your car owners manual.

Open

Important

Script should support manufacturer specific queries for Fuel level, mileage, state of charge (for hybrid (HV) or electric vehicles (EV)), driver belt status, passenger belt status on Ford, Renault, Volvo, Land Rover, Jaguar, GM, Audi, VW, Skoda, Mazda, Mitsubishi, Nissan, Toyota, Kia, Hyundai, Subaru and Fiat Vehicles. Due to limited testing, officially supported vehicle list is limited.