Skip to content

Quick start

Booster cable The openOBD service is built upon gRPC technology. With openOBD you can build automated and guided diagnostic procedures that improve the efficiency and reliability of your remote diagnostics service.

Not yet a Jifeline Networks Partner?

If you want to test with openOBD, you need to have access to a partner dashboard of Jifeline Networks.
Please check https://jifeline.net/en/create-your-own-network/

The implementation of these procedures is done by creating an openOBD session on your ticket. This session is can be controlled with your own client software. It is possible to communicate with the vehicle and interact with the customer. This 'quick start' will bring you up and running using our example Python implementations.

Jifeline support site Jifeline Networks!

If you are a partner of Jifeline and not already a member, you can subscribe on the Jifeline support site. This site gives you, as a partner, more insight in things like: Jifeline support

  • Connecting your J-ReX
  • Creating tickets
  • Managing users
  • Troubleshooting

Go to Jifeline Support

Requirements

  Before you start, please check if you meet the following requirements.

You are a partner of Jifeline Networks

For now, the openOBD service is offered to Jifeline Network partners (a.k.a. providers). If you are currently not part of the Jifeline Network, please check https://jifeline.net/en/create-your-own-network/.

You have access to a J-ReX Vehicle Communication Interface (VCI)

The J-ReX interface You need a J-ReX connector (VCI of Jifeline Networks) to start developing for openOBD. One of the key features of openOBD is that you can write your own client software to communicate with a vehicle. Th J-ReX should be connected to the 16-pin OBD-socket in the vehicle. The J-ReX should have a correctly configured wifi or ethernet connection. (See Jifeline Support for more help on this)

You have access to the API credentials

You need access to the Partner API of Jifeline Networks. In the examples on this website the credentials are loaded from environment variables. For development purposes it is good practice to store these environment variables in a single file and load them into memory at the start of your program.

The values that need to be present are given below in openobd_credentials.env. Steps to acquire the credentials from the Jifeline Partner dashboard are given here.

OPENOBD_PARTNER_CLIENT_ID=<Client ID>
OPENOBD_PARTNER_CLIENT_SECRET=<Client Secret>
OPENOBD_CLUSTER_ID=001
OPENOBD_GRPC_HOST=grpc.openobd.com