jifeline-partner-portal

Images for commercial use

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 10 Mar 2025 11:39:33 GMT

Images for commercial use

These images can be used for commercial purposes.

Outsourced-Notes

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Wed, 12 Jul 2023 12:52:16 GMT

Outsourced-Notes

Notes and attachments also allows you to save notes on an insourced ticket that becomes visible to the service provider that outsourced the ticket.

This functionality can work with all types of notes such as photos, videos, documents and text.

In the following example, a ticket was sent from service provider A to B.

Service provider B saves a note on the ticket and sets the note to public(see picture below).

In the dashboard of service provider A, the tab ''Outsourced notes'' appears

Here you can see the note that Service provider B saved on the ticket(see picture below).

For additional explanation, you can always watch our Jifeline instructional video on the subject (see below).

UDS protocol guide

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 14:47:07 GMT

UDS protocol guide

Introduction to UDS protocol

UDS stands for Unified Diagnostic Services. This protocol is defined in ISO-14229-1 standard. It is an independent protocol that allows an ECU (CAN) to communicate with a diagnostic tool. This makes it possible to communicate with any car brand. Besides UDS, KWP2000 and GMLAN are also protocols which can be used by vehicles. But because they are more outdated than UDS, many manufacturers don’t use them anymore. UDS is more up to date and controlled by ISO. This is why almost every car manufacturer uses it and have stopped using KWP2000 or GMLAN. In the live data log it is possible to read the UDS messages that are being sent to the vehicle and back.

To be able to read UDS you have to understand its structure. Each new line in the log, specifically during communication between vehicle and diagnostic tool/script, is a new message. This line always starts with a time stamp of when it was sent. behind this it is stated between which components the message is sent. For example, the sender is displayed first with an arrow pointing to the recipient. These messages are sent between remote and local (diagnostic tool/script). Behind the clarification of which components are involved is the word “DATA” with an arrow shown.

This is visable in the example below, the words that are described in this message are surrounded in red. After this arrow the contest of the message is displayed. The first two words in small letters (mod and cmd) and the info behind in parentheses are for the server and internal use. The third word “args” defines the ECU identification. This tells you to which ECU in the CAN-bus the message is being sent. You can find more info about this below. Behind the last word (data) in parentheses, the UDS message is displayed. This message starts with 0x and after this the content of the message is displayed (explained under “message frame format”).

Message frame format

The UDS protocol is a message based protocol to communicate with a vehicles ECU and its on-board diagnostics. Message based protocol means the communication is transfer by messages. At Jifeline we have our own built in-house format of displaying the UDS messages. When the diagnostic tool requests anything, it sends a request message to the vehicle.

When received, the vehicle sends a message back with the requested data or confirmation. A message is made out of 8 bytes (sometimes this is exceeded, this is because of the plugins/profiles Jifeline uses). Displayed in hexadecimal format (explained below). These codes can translate to a meaning or definition. There are examples on the bottom on the page.

Requist message frame

A request message is a message going from local to remote. It starts with a service identifier (SID). It is the first byte of the message. This is the “ID” of the function group and is so connected with a request. The SID indicates if there is a Sub-function byte. This is the next byte in the message. It depends on the specific SID if it has a Sub-function byte or not. The remainder of the bytes defines the data parameters. The SID’s and sub-functions that are defined by ISO are visible in the scheme below.

Response message frame

A response message is a message going from remote to local. The response format has 2 possibility’s: a positive response and a negative response. The response answers to the last send request.

The first Byte of the positive response is a SID. To indicate the request has been successfully executed it will add 40 to the SID byte (for example: when the request SID byte was 22, the response byte will be 62). This is followed a Sub-function byte, but only if the SID had one. If so, the sub-function will be shown unchanged in the second byte. After that a data response code will be shown, if this was requested. If this wasn’t requested the message will only contain a SID + 40 and Sub-function to indicate the task was successful. Below you can find a scheme with common data response codes.

With a negative response you will see another message. This is when the ECU or OBD could not preform the request or the request message was not a proper format. In this case the response message will start with the byte 7F. The following byte will be the requested SID. The remainder of the bytes will show a Negative response code with details of why the request was not successfully completed.

HEX code

Hexadecimal is a math and computer used numbering system. It expands the common numbering system by adding letters to it. The common numbering system uses 0 to 9 which gives you 10 options per symbol. Hexadecimal replaces 10 to 15 with the letters A to F. This represents a wider numeral system. this means there are now 16 options per symbol. UDS protocol uses bytes of 2 hex numbers. This means the possible spread isn’t 00 to 99 but it is 00 to FF. Giving it 256 possible codes per byte instead of 100.

ASCII

The data you receive from the ECU is written in HEX. Whenever you request data or information like the VIN of the vehicle, the data will response with a HEX code. When you convert this to ASCII, the real VIN will show up (Like in example 2). Converting a HEX line can be done with a converter tool. On the internet you can find these tool by searching for: HEX to ASCII converter. There are also conversion tables available on the internet where you can look thru al the HEX to ASCII characters.

Notice that not everything can be converted. The SID and sub-functions are defined by UDS and have a definition that is separate from HEX. This also goes for the common response codes. Besides that, it isn’t specified what can be converted. For example, when receiving a VIN, you convert it from HEX to ASCII. But when receiving a milage, you convert from HEX to decimals. In most cases you need to convert it to find out if it Is possible. When converted and not human-readable we can assume that the ASCII conversion is not valid for this case (Like: ” % Ö Ý # @). In these cases in can be converted to decimals or it is a UDS/manufacturer defined code.

ECU identification

In the message, the word args is displayed before data. This indicates to which ECU or server within the vehicle the message is being send. Each ECU has its own request and response address. So is there an engine control module, gateway module or a Milage Recalibration. The identification isn’t specified. This means manufacturers all use other identifier adresses. For example, when displayed: args[0x07E0,0x00,0x00,0x00], the first code indicates the ECU. In this case: 0x07E0. For multiple manufacturers this is the ECM (engine control module). This means the request will be sent to the ECM.

SID identification

In this window are all the ISO defined SID visible. When the SID isn’t specified in this window it is bonded to a manufacturer.

Sub-functions

In this window are all the sub-functions visible that are connected to a SID above. When the sub-function isn’t specified in this window it is bonded to a manufacturer.

Function description

Here you can find a description for all the SID's and Sub-functions.

Common response codes

In this window are all the ISO defined response codes visible. When the code isn’t specified in this window it can be bonded to a manufacturer or it is data which can be translated.

Examples

Example 1: request extend diagnostic session

Request message

data[0x1003]

SID = 1st byte = 0x10 – has sub-function

SBF (Sub-function) = 2nd byte = 0x03

0x03 means Extended diagnostic session

Positive response message

data[0x5003]

Response SID = 1ste byte = 0x50 = positive response

SBF = 2nd byte = 0x03

Negative response message

data[0x7F10XX]

0x7F = 1st byte = negative response byte

SID = 0x10 = 2nd byte

0xXX = this is an example for last bytes = indicates a negative response code

Example 2: requesting a VIN

Request message

data[0x22F190]

SID = 1st byte = 0x22 = Read Data By Identifier = No SBF

0xF190 = 2nd & 3rd byte = read VIN identifier

Response message

data[0x62F1905756575A5A5A43445A4D57303030303030]

Response SID = 1ste byte = 0x62 = positive response

0xF190 = 2nd & 3rd byte = response to read VIN identifier

0x5756575A5A5A43445A4D57303030303030 = data response code = Vehicle VIN in HEX code

Possible to translate with ASCII (HEX to ASCII converter)

Real VIN becomes = WVWZZZCDZMW000000

Example 3: requesting vehicle-manufacturer-specific ECU hardware number (serial number)

Request message

data[0x22F191]

SID = 1st byte = 0x22 = Read Data By Identifier = No SBF

0xF191 = 2nd & 3rd byte = read vehicle-manufacturer-specific ECU hardware number

Response message

data[0x62F1913557413936323130303020]

Response SID = 1ste byte = 0x62 = positive response

0xF191 = 2nd & 3rd byte = response to read vehicle-manufacturer-specific ECU hardware number

0x3557413936323130303020 = data response code = vehicle-manufacturer-specific ECU hardware number in HEX

Possible to translate with ASCII (HEX to ASCII converter)

Real vehicle-manufacturer-specific ECU hardware number becomes = 5WA962000B

Example 4: Programming date when ECU was last programmed

Request message

data[0x2EF199210101]

SID = 1st byte = 0x2E = Write Data By Identifier = NO SBF

0xF199 = 2nd & 3rd byte = write programming Date Data Identifier

0x210101 = date (written as: year, month, day) = in this case: 1st of January 2021

Response message

data[0x6EF199]

SID = 1st byte = 0x6E = positive response

0xF199 = 2nd & 3rd byte = response to write programming Date Data Identifier

Example 5: check if tester is present. (i.e. check if remote is still connected to CAN-bus)

Request message

Data[0x3E80]

SID = 1st byte = 0x3E = Tester Present = has SBN

SFN = 2nd byte = 0x0 = zero Sub-Function without response message

No response message

Live data log

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 14:47:05 GMT

Live data log

The communication between the remote and local is visible in this window. To show the live log in your ticket screen Click the 3 dots in the upper right corner and enable the button what says ''Show live log''.

The data that you can see in this window is communication between remote and local. This communication is done with a communication protocol. UDS protocol is most used to communicate. nderneath the live data window you will find more options.

Open comments

By pressing “open Comments” you will open a small window (shown above). In the bar you can enter a text and when you press “add comment” .this text will be displayed is the live data log. This marker in the live log do not interfere with the running data.

Copy

The green button with “copy” on it gives you the possibility to copy the complete live data window. Everything that is displayed in the window at that moment will be copied. The copied text can be pasted in any document you like. The best way to read the copied data is by using the program Notepad++.

Clear log

The yellow button “clear ” deletes all the lines in the live data log. New data will be shown when there is still communication between local and remote.

Transponder key programming for Toyota Aygo I & II based vehicle models

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:48 GMT

Transponder Key Programming for Toyota Aygo I & II based vehicle models

Partners in the Jifeline network have access to the so-called Automated Functions via Jifeline Networks. In this article we describe the automated function for the transponder key programming for vehicles that are based on the Toyota Aygo I and II.

Citroën C1 I
Citroen C1 II
Peugeot 107
Peugeot 108
Toyota Aygo I
Toyota Aygo II

The guided process includes following steps:

Programming of the new transponder key, a programmed master key must be available at the vehicle to start the programming
Guided instruction for synchronizing the new remote control
The ticket is handled fully automatically in a few minutes

In case the guided process is cancelled?

The most common problem is not having a programmed master key with the vehicle. If a master key is not present, then the control unit of the immobilizer has to be replaced. This control unit is located under the dashboard, at the level of the instrument cluster. The upper part of the dashboard has to be removed. Low board voltage is also a common problem too. This can be easily solved by connecting a good battery charger.

Transponder key programming for Renault KWP2000 vehicle models

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:47 GMT

Transponder key programming for Renault KWP2000 vehicle models

Clio - III
Kangoo Grand/Express
Master - III
Modus
Megane - II
Scenic - II
Twingo - II

The guided process includes following steps:

Programming of the new transponder key and the remote control
The ticket is handled fully automatically in a few minutes

It is not necessary to have the electronic security code available with the vehicle.

Transponder key programming for Renault K-line vehicle models

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:45 GMT

Transponder key programming for Renault K-line vehicle models

Clio - II
Espace - IV
Kangoo
Laguna - II
Master - II
Dacia Sandero - I
Trafic - II

The guided process includes following steps:

Programming of the new transponder key and the remote control
The ticket is handled fully automatically in a few minutes

It is not necessary to have the electronic security code available with the vehicle.

Transponder key programming for PSA vehicles (BSI)

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:42 GMT

Transponder key programming for PSA vehicles (BSI)

All models having a BSI on board

The guided process includes following steps:

Reading of the transponder code, a working key is required
(If no working key is available, the user shall enter the PIN code)
(for k-line cars the PIN code is required!)
Programming of the new transponder key and the remote control
The ticket is handled fully automatically in a few minutes

It is not necessary to have the electronic security code (transponder code) available with the vehicle.

In case the automatic procedure is cancelled?

When a procedure cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason

Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on
It was not possible to complete the service automatically, we will now connect you to a live technician to assist you further.
Unfortunately, it was not possible to perform the procedure automatically
In many cases, the mechanic at the vehicle made an unexpected mistake

One of the conditions to start the job is not correct.
Some of the required modules cannot be found.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port.

Transponder key programming for Opel vehicles (GMLan)

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:38 GMT

Transponder key programming for Opel vehicles (GMLan)

Opel Astra-H
Opel Corsa-D
Opel Zafira-B

The guided process includes following steps:

Reading of the security code, a working key is required
(If no working key is available, the user shall enter the PIN code)
Programming of the new transponder key and the remote control
The ticket is handled fully automatically in a few minutes

It is not necessary to have the electronic security code (pin code) available with the vehicle.

In case the automatic procedure is cancelled?

When a procedure cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason

Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on
It was not possible to complete the service automatically, we will now connect you to a live technician to assist you further.
Unfortunately, it was not possible to perform the procedure automatically
In many cases, the mechanic at the vehicle made an unexpected mistake

Transponder key programming for Hyundai / Kia vehicles

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:36 GMT

Transponder key programming for Hyundai / Kia vehicles

Both k-line and CAN immobiliser systems

The guided process includes following steps:

Reading of the pin code, a working key is required
(If no working key is available, the user shall enter the PIN code)
Programming of the new transponder key and the remote control
The ticket is handled fully automatically in a few minutes

It is not necessary to have the electronic security code (pin code) available with the vehicle.

In case the automatic procedure is cancelled?

When a procedure cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason

Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on
It was not possible to complete the service automatically, we will now connect you to a live technician to assist you further.
Unfortunately, it was not possible to perform the procedure automatically
In many cases, the mechanic at the vehicle made an unexpected mistake

Transponder key programming for Fiat

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:34 GMT

Transponder key programming for Fiat

Non security gateway vehicles
Fiat 500 (312)
Fiat 500L (351, 352)
Fiat Doblo (263)
Fiat Ducato (250)
Fiat Panda (312, 319)

The guided process includes following steps:

Retrieving the electronic security code from the vehicle. Reading of the pin code, a working key is required (If no working key is available, the user shall enter the PIN code)
Programming of the new transponder key
All transponder keys must be available at the vehicle during the programming session. Transponder keys that are not available during the programming session will be permanently deleted
Guided instruction for synchronizing the new remote control
The ticket is handled fully automatically in a few minutes

In case the automatic procedure is cancelled?

When a procedure cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason

Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units .
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on
It was not possible to complete the service automatically, we will now connect you to a live technician to assist you further.
Unfortunately, it was not possible to perform the procedure automatically
In many cases, the mechanic at the vehicle made an unexpected mistake

VAG automated towbar coding

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:32 GMT

VAG automated towbar coding

Partners in the Jifeline network have access to the so-called Automated Functions via Jifeline Networks. These are automated functions such as towbar coding for vehicles on the VAG PQ and MQB/MLB platforms.

The availability of an automated function can easily be checked via the outsource menu. You can also use the blue button in the product widget to start the feature.

Coding includes

Battery voltage check, we encourage to use a battery support charger
If the trailer module is not detected, the user is assisted in the troubleshooting.
Coding of all relevant modules of the vehicle
Final check of lighting, among other things, together with the installer
Customer communication is handled automatically, see setting s

Why automated functions

No local needed in the connection so it remains available for other jobs
No diagnostic tool needed on your side so you have those available for other jobs
Your experienced technicians can focus on other more complex jobs
Automated coding of the tow bar function in the vehicle electronics in a matter of seconds
The ticket is handled fully automatically in a few minutes

In case the automatic coding is cancelled?

When coding a vehicle cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason
Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on

The automated task has only been partially executed. The ticket will be returned to your dashboard. Of course you can still outsource the ticket to Jifeline Remote Diagnostics to finish the job.

Not all coding data is available. The robot cannot code the vehicle.

In such a case, you can either complete the ticket yourself with your own team or outsource it to Jifeline Remote Diagnostics. In the latter case, the database will also be updated with the newly obtained coding data.
One of the conditions to start the job is not correct.
If the vehicle is equipped with SFD protected control units proceed as follows.

SFD

If the vehicle is equipped with SFD protected control units proceed as follows.

1.First, access to the SFD protected modules must be granted. Please unlock SFD Modules with OE diagnostic equipment. In most cases, the following control units are involved:

01 Engine Control Module 03 Brake Electronics Module 09 Central Electronics 17 Instruments 19 Gateway 7E Info Display

2. Second, after you have enabled the vehicle's control units, you can outsource the relevant ticket to Automated Functions

In case you outsource a ticket to Automated Functions where the SFD protected control units are not yet enabled, the following message will be shown to the relevant operator:

3. Third, make sure all relevant SFD control units are enabled, then outsource again to Automated Functions via the blue button in the product section

The automated process will now complete the coding and relevant checks

ℹ️ If you enable the auto-close functionality, the ticket will be completed automatically. The auto-close function can be found under settings, outsourcing tab.

PSA automated towbar coding

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:30 GMT

PSA automated towbar coding

Partners in the Jifeline network have access to the so-called Automated Functions via Jifeline Networks. These are automated functions such as towbar coding for vehicles on the PSA platform.

The availability of an automated function can easily be checked via the outsource menu. You can also use the blue button in the product widget to start the feature

Citroën - all models with a PSA BSI
DS - all models with a PSA BSI
Opel - Corsa-F, Crossland, Grandland, Mokka (2020 >), Vivaro Life, Zafira Life
Peugeot - all models with a PSA BSI
Toyota - PROACE

Coding includes

Coding of the vehicle is necessary for the correct operation of the lighting on the trailer.
Coding of all relevant modules of the vehicle, including the Tailgate module
Final check of lighting, among other things, together with the installer
Customer communication is handled automatically, see setting s

Why automated functions

No local needed in the connection so it remains available for other jobs
No diagnostic tool needed on your side so you have those available for other jobs
Your experienced technicians can focus on other more complex jobs
Automated coding of the tow bar function in the vehicle electronics in a matter of seconds
The ticket is handled fully automatically in a few minutes

In case the automatic coding is cancelled?

When coding a vehicle cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason
Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on

The automated task has only been partially executed. The ticket will be returned to your dashboard. Of course you can still outsource the ticket to Jifeline Remote Diagnostics to finish the job.
Not all coding data is available. The robot cannot code the vehicle.
Code the car yourself, make sure you update the coding database by running the script in learning mode
In case your are unsure about the coding, ask your supervisor to assist

One of the conditions to start the job is not correct.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port. A common problem is that some of the required modules cannot be found.

Mercedes-Benz automated towbar coding

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:28 GMT

Mercedes-Benz automated towbar coding

The availability of an automated function can easily be checked via the outsource menu. You can also use the blue button in the product widget to start the feature

A-class (W176, W177)
B-class (W246, W242, W247)
C-class (W204, W205)
CLA-class (C118)
E-class (W212, W213)
GLA-class (X156, H247)
GLC-class (X253, C253)
S-class (W222)

Coding includes

Battery voltage check, we encourage to use a professional battery support charger
Coding of all relevant modules of the vehicle
Final check of lighting, among other things, together with the installer
Customer communication is handled automatically, see setting s

Why automated functions

No local needed in the connection so it remains available for other jobs
No diagnostic tool needed on your side so you have those available for other jobs
Your experienced technicians can focus on other more complex jobs
Automated coding of the tow bar function in the vehicle electronics in a matter of seconds
The ticket is handled fully automatically in a few minutes

In case the automatic coding is cancelled?

When coding a vehicle cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason
Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on

The automated task has only been partially executed. The ticket will be returned to your dashboard. Of course you can still outsource the ticket to Jifeline Remote Diagnostics to finish the job.
Not all coding data is available. The robot cannot code the vehicle.
It might be neccessairy to add code 550 (+1FN) to the VEDOC system

One of the conditions to start the job is not correct.
Most common problem is that the ignition is not in the right position.
Switch off the ignition, lock the vehicle and wait two minutes. Then try again.

Ford automated towbar coding

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:25 GMT

Ford automated towbar coding

Partners in the Jifeline network have access to the so-called Automated Functions via Jifeline Networks. These are automated functions such as towbar coding for vehicles on several Ford platform.

The availability of an automated function can easily be checked via the outsource menu. You can also use the blue button in the product widget to start the feature.

B platform
Fiesta VIII (2017 >)
C platform
Focus IV (2019 >)
Kuga (2020 >)
D platform
Galaxy (2015 >)
Mondeo V (2015 >)
S-Max (2015 >)
Full size van
Transit (81) (2014 >)

Coding includes

Battery voltage check, we encourage to use a battery support charger
Coding of all relevant modules of the vehicle
Final check of lighting, among other things, together with the installer
Customer communication is handled automatically, see setting s

Why automated functions

No local needed in the connection so it remains available for other jobs
No diagnostic tool needed on your side so you have those available for other jobs
Your experienced technicians can focus on other more complex jobs
Automated coding of the tow bar function in the vehicle electronics in a matter of seconds
The ticket is handled fully automatically in a few minutes

In case automatic coding is cancelled?

When coding a vehicle cannot be performed by the automated service provider, note the following:

The robot's last chat message gives an indication of the cancellation reason
Failed to establish communication with control modules in vehicle.
No communication is possible with the vehicle's control units.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port
Check the workshop's internet connection
Ensure that the ignition is correctly switched on

The automated task has only been partially executed. The ticket will be returned to your dashboard. Of course you can still outsource the ticket to Jifeline Remote Diagnostics to finish the job.
Not all coding data is available. The robot cannot code the vehicle.
Code the car yourself
In case your are unsure about the coding, ask your supervisor to assist

One of the conditions to start the job is not correct.
Check that the VCI (J-ReX) is properly connected to the vehicle's OBD2 port. A common problem is that some of the required modules cannot be found.

How to setup automated functions

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 10:41:23 GMT

How to setup automated functions

Automated functions

Partners have access to the so-called Automated Functions via Jifeline Networks. These are automated functions such as towbar coding for Audi, Citroën, Dacia, Ford, Nissan, Mercedes-Benz, Opel, Peugeot, Renault, Seat, Skoda and Volkswagen models.

To gain access to the Automated Functions select the Automated Functions partner from the dropdown menu in your catalog. If your catalog does not have the Automated Functions configuration please contact Jifeline Networks.

Set up in your product catalog

In your product catalog for the “Tow Bar Coding (Aftermarket equipment)” product, you will be able to select “Automated Functions” as an outsource partner. If you select “Automated Functions” in the next step you can make some price settings as mentioned before in this manual.

Auto close the ticket when it is finished

You can define what happens with a ticket when Automated Functions finished it. These setting can be done in the settings menu on the outsourcing tab.

Automated chat messages

The Automated Functions "operator" can use the chat to keep the garage owner informed of the ticket's progress. To enable this, go to the " outsourcing settings " tab.

Since this is an automated chat, only messages are sent. If you send a message to the automated operator (Robin Bot) it will not be read.

When an automated service is running, the chat is in read-only mode. Thus, the garage operator cannot send messages to the operator .

Monitor automated function tickets

You can designate an operator to monitor the tickets received through Automated Functions. This setting is also found on the " o utsourcing settings " tab of the settings page.

What happens if the automated function cannot be completed?

If the Automated Function cannot code the vehicle, the process is aborted. The ticket will be cancelled. You then have the following options to still get the vehicle coded:

You choose to carry out the coding independently with your technicians and diagnostic equipment
You outsource the ticket to Jifeline Remote Diagnostics. In this case, we will use the coding information obtained to expand our database

Customer perspective

Below is an example of an automatic towbar coding on a Peugeot 308 II. In this example the service provider has enabled the auto-close setting in the Outsourcing settings tab. Off course the instructions for your client are available in several languages.

Expose product price list as REST API

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 07:05:45 GMT

Expose product price list as REST API

With this feature, partners can offer their customers the product catalog by implementing it on a website. This product catalog contains descriptions and prices of all services offered, sorted by car.

How to offer as a partner?

Partners have the following option to select via Settings-> Settings-> General:

Expose product price list as REST API (Make product price list public through REST API)

With this option, a partner chooses to publish the price lists

Embed iFrame

By means of a ready-made iFrame: the partner can implement a block of code offered by Jifeline in the website. The implementation of an iFrame is simple and does not require substantial IT investments.

Embed following source URL for a price list in English:
"https://provider-pricing-list-001.jifeline.cloud/pricing/ < provider-uuid > /vehicle?locale=en-GB&prices=true&branding_profile_id= branding_profile_uuid ".

Where can I find my provider-uuid ?
The branding_profile_id is visible in the URL when editing a branding via your Partner Portal
(example: https://......../branding/ 43174954-e1a7-4cb0-a1ef-8128a0ad582f /edit)

The advised iframe height is =< 500 px.

Some elements will be hidden if iframe height is incorrect.

Query parameters

Rest API

Or partner chooses to make implementation himself using the offered REST API URLs. The documentation with all necessary information for partners can be found at: https://provider-admin-api.jifeline.com/api/doc/provider- admin A username and password for accessing the API documentation can be found in the Settings-> Settings-> API page .

How to use as an end user (customer)?

The underlying structure and use of this product catalog is almost identical to the selection menu of the mobile application. The end user indicates which car a service is to be searched for. Choosing a specific car is done in four steps:

Car brand
Model
Type
Engine type

(eg 1. Renault 2. Laguna 3. Coupe (DT0 / 1) 4. 2.0 dCi)

After choosing a level, the options of the higher level are displayed. When all levels are completed, an overview of all available services can be displayed, with descriptions and prices.

Partner admin API

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 05 May 2023 07:05:43 GMT

Partner admin API

The Partner Admin API can be used to handle administrative matters such as:

Customer and connector registrations
Ticket processing
Invoicing
Pricing
Voucher creation

More information regarding access to this API and the documentation can be found here .

Wifi router TCP / UDP settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 14:25:33 GMT

Wifi router TCP / UDP settings

TCP / UDP settings

For a correct operation of the remote diagnostics application you are advised to perform following TCP/UDP port settings in your WiFi router. Open outgoing TCP/UDP ports:

Mandatory

443 user interfacing
46329 (CAN Bus data -AES encrypted)

Alternatively if port 46329 fails

80 (optional, port 80 is fall-back for port 46329, CAN Bus data - AES encrypted)

Test the portscan in a browser

https://portscanner.prd.jifeline.cloud:46329/

Wifi netwerk security

The wifi security should be set to WPA/WPA2.

Host

The "local" and "remote" connectors connect to passthrough.jifeline.com.

Network Band

The remote only supports a network band of 2.4GHz . This means that it will not be able to connect to a 5 GHz Network.

OTA firmware update

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 14:23:17 GMT

OTA firmware update

From time to time we will perform an OTA (“Over The Air”) update on all remotes. To date, there has been no clear indication that the remote is performing an update. To solve this problem we introduce the beeper and the blue front LEDs.

A blue front LED and a short beep indicate that the remote is performing an update. It is then
important not to disconnect the remote from the car or the internet to prevent the remote from
getting stuck in an update.

The update process takes an average of 1-2 minutes (depending on the speed of your internet
connection). The length of the update process depends on how regularly you use the remote. It
can happen that a remote is updating for a longer period of time because the remote has not
been used for a long time. If the update is done correctly, the blue LEDs will return to their
original green color.

So if you encounter the blue LEDs and the beeper while using the J-ReX remote, it is important
to patiently wait for the update.

Connecting the OBD-II local

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 14:23:14 GMT

Connecting the OBD-II local

The local can be easily connected:

Connect power cable
Connect your local with your ethernetcable directly to your network

Once the local is connected and powered it will appear in Your dashboard.

How to connect the wireless remote to a workshop’s 2.4 GHz WiFi network?

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 14:23:13 GMT

How to connect the wireless remote to a workshop’s 2.4 GHz WiFi network?

Instruction

1. Connect the J-ReX remote to a vehicle’s OBD-II connector.

2. Reset to default settings by using the reset pin. Keep the reset button pressed, approximately 3 seconds, to reset. The green LED will blink once a second.

3. Now open the WiFi settings menu on your phone and connect to Connector<connector-ID>.

4. Open google chrome on your phone and go to connector.help

5. Now select the preferred 2.4 GHz WiFi network you would like to connect to and fill in the password (Please note that it is sensitive to capital letters).

6. The green LED near the ethernetport of the interface should light up constantly once it's connected.

How to link a (wireless) remote to a client?

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 14:23:11 GMT

How to link a (wireless) remote to a client?

Instruction

Go to the clients’ section in the Partner dashboard .

Select the client that you would like to add the (WiFi) remote to.
Open the “Connector” tab.

+ Add connector (usb and/or WiFi remote)

The following screen shows up:

If a remote is added, a PIN will be generated automatically. This pincode can be changed manually.

User name and password

When a WiFi connector is linked to a customer, the system sends an email with password instruction to the e-mail address that is listed on the WiFi remote tab.

Make sure the email address is unique and correct
If you see something such as user_91021@example.com you should check for a double customer record in your partner dashboard. If this is not the case please contact Jifeline Networks Support for further assistance.
If necessary a password reset request can be forced from this tab as well.

Creating a ticket using a wireless remote

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 12:35:48 GMT

Creating a ticket using a wireless remote

Connect the wireless remote to the vehicle's OBD-II port
Open a browser and type in

* The value "Brand name" on the settingspage [add link to Manage Settings page] of your branding profile is the place holder for mycompany in the above URL.

3. Log in using user name and password.
Instructions how to setup the user name and password can be found here .

4. Select the remote interface from the connector list view

5. The application will now try to read the VIN of the connected vehicle. In case the VIN cannot be read the end user has to enter the VIN manually.

6. Select the service from the catalog

7. Create the ticket

In the video below you will see step by step how to create a ticket.

Preferred currency

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Thu, 04 May 2023 12:35:45 GMT

Preferred currency

Using the set preferred currency, the Customer Portal displays the amounts of the services in the preferred currency of the customer. This is particularly useful for Service Providers with a product catalog in the currency "euro" who have customers in the Nordic area.

This setting is saved on the Base Client detail page.

Setting up insource / outsource relationships

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:38 GMT

Setting up insource / outsource relationships

Setting-up an insource / outsource relationship

In the Jifeline system, you have the option to outsource tickets to other Jifeline partners. For this, an insource / outsource relationship needs to be set-up, which requires the following steps:

Agreeing the conditions with your insource / outsource partner (you / your partner)
Connecting you as possible ‘Service Providers’ to each other (Jifeline)
Setting-up each other as ‘Client’ in the system (you / your partner)
Linking the ‘Service Provider‘ to the relevant ‘client’ (you / your partner)

1.Agreeing on the conditions (by partners)

Jifeline can facilitate the outsourcing of tickets between partners / dashboards, but does not facilitate administrative aspects like invoicing etc.. For this, the partners need to agree amongst themselves about topics like which tickets can be outsourced to each other, reporting, invoicing etc.

2. Connecting the insource / outsource service providers (by Jifeline)

When both partners agree, they should inform Jifeline (via support@jifeline.com ). Jifeline will then connect both partners as ‘insourcing / outsourcing’ Service Providers.

3. Setting-up each other as 'client' (by partners)

Each partner need to set-up the other as ‘client’ in their dashboard.

4. Lining the 'client' and the 'service provider'

To be able to forward tickets, both partners need to connect the newly created client to the insourcing / outsourcing Service Provider.

For this:

Go in the Jifeline Dashboard to ‘Settings’ (in sidebar on the left of the screen)
Go to the tab ‘Insourcing links’
Look-up the right Service Provider, and click ''Edit insource setting''.
Set up the newly created client as the Target client.
Set up the Default product(this is the product that will be attached to the insourced ticket, if the product is not active in your catalog). We suggest to use '100120, Remote Diagnostic Support for this.

Don't forget to click 'update' on the bottom of the page.

When both you and the other partner have done this, it is possible to outsource a ticket to eachother.

Outsource settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:37 GMT

Outsource settings

Define whether your customer is allowed to receive automated chat messages from Automated Functions. Furthermore, you can also set which operator is responsible for the automatically outsourced tickets.

Service message settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:37 GMT

Service message settings

Service message

You can setup a service message that will be displayed to your end users.

The service message is shown to your customer after logging in to the web application.

Insourcing settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:35 GMT

Insourcing settings

This option enables you to manage your Insourcing Partners. Each Partner can ask for insourcing Partners by sending an e-mail to Jifeline Networks.

Jifeline Networks will activate your request, for each partner with whom you have an insource relationship, you need to set the following:

Target client
This links the incoming ticket to a base client.
Default product
This setting is necessary to enable ticket exchange with a service provider that still works with the first generation product catalogue. When the service provider tries to outsource a ticket to you, the configured product is placed on the ticket as the default product. Make sure that you have configured the "default product" correctly in your product catalog.
The "default product" setting is also used to enable ticket exchange with a service provider that has only partially filled its catalogue and therefore cannot find a suitable product in case of ticket outsourcing.

Outsourcing links

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:34 GMT

Outsourcing links

This option enables you to manage your Outsourcing Partners. you can ask for Outsourcing Partners by sending an e-mail to Jifeline Networks.

After we have got permission of both parties we can enable the Outsourcing link.

Manage "auto-closing" of tickets

On this page you can set whether a ticket that comes back from "outsource" should be closed automatically.

The ticket will be closed automatically only if:

The product(s) on your ticket match to the products on the partner ticket;
The partner to whom the ticket was outsourced closed the ticket;
You have enabled the "auto-close" functionality in the settings tab*.

This is where the new catalog and product management becomes very useful . Imagine that you outsource a ticket that involves a tow bar coding job to Automated Functions . Once the ticket has been completed and closed by Automated Functions, it will be automatically closed at your dashboard.

Messenger settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:33 GMT

Messenger settings

The settings affect the behavior of the Messenger in the remote diagnostic application. We have enabled both features by default.

More information about the Messenger can be found here .

The use of file sharing will be billed through a monthly fee.

For Fee prices see the price list.

API settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 14:40:29 GMT

API settings

Partner API (v2)

Here you can manage your partner API credentials.

Per Service Provider multiple credentials can be created
To add new credentials click the button "Add new API credentials"
The new credentials will be sent via e-mail

The developer documentation for the Partner API (v2) can be read here.

Partner API (v2) documentation

Legacy API (v1)

Request API data access via e-mail. Enter the email address where you want to receive API credentials.

Your provider UUID can be found on the API tab. It is displayed in the API username field.

Manage branding settings

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 12:00:39 GMT

Manage branding settings

Here you can manage settings for your branding. It is possible to have a multi-branded dashboard. In your settings, you will already find the first branding which can be styled with your colors and logo.

If an extra branding is needed, you can send us a request and we will open up an extra branding* for you.

Check the branding settings in your partner dashboard: > settings > branding.

* Refer to Jifeline Networks Pricing

Profile Description

The Profile Description is used in several places in the application. E.g. in the ticket dashboard to link a ticket to a branding. Furthermore, we also show the Profile Description in the header of the Customer Portal.

Brand name

The brand name is used as your display name for administrative and communication purposes. It also determines the prefix of your portal URL (https://brandname.obd.help).

Theme color

The color of the progress bar and icons is based on the theme color. In this example orange.

Headed color

The color of the banner of the password reset page is based on this header color.

Portal header logo

Make sure your logo looks good on a white background.

Terms of service URL

This URL is shown in the customer portal. You can set General Terms and Conditions per branding. To do this, go to "Branding settings" and then set up the "URLs" tab.

Make sure that you include "https://" in the URL.

Your customer must accept the Terms and Conditions before the "create ticket" button becomes available. When your customer hovers the mouse over the text "Terms and Conditions", a clickable link appears.

This URL is shown in the customer portal.

Wireless Interface Instructional Video URL

This custom URL is used in e-mail communication to new customers. When left empty, the default URL is used.

Remote Acces URL

This URL is shown in the customer portal. This can be used to offer i.e. Teamviewer support in case you need to assist the end user.

Help Center URL

This URL is shown in the customer portal. Create a short cut to your company branded help center or manuals. Here is an example: https://support.jifeline.help .

Set branding profile margin

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 12:00:38 GMT

Set Branding Profile Margin

Branding pricing

Different price settings can be made on a branding. This can be useful when, as a service provider, you work with so-called resellers.

A markup on the gross price can be set, both a monetary and percentage markup
Furthermore, a discount percentage can be set for the branding. Customers that are connected to the branding will get a net price which is calculated as follows: net = gross * (1 - discount)

In this table, you can see what percentage topping you need to give to achieve the desired gross price.

Welcome message

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 12:00:37 GMT

Welcome message

Enabale automatic welcome message

Here you can set an automatic welcome message. The message will be posted in the chat as soon as a ticket is created.

Transactional e-mail messages

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 12:00:35 GMT

Transactional e-mail messages

Customers receive transactional email messages. The messages will be sent on behalf of the respective service provider.

Connector registration

When a connector is linked to a base client, the following message is sent.

Password reset

In the case where an end user requests a password reset, the following message is sent.

Adding a discount code

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 10:45:10 GMT

Adding a discount code

You can easily add a discount code away by clicking "Add new code". A pop-up screen will allow you to make the desired settings for the new discount code.

A specific discount percentage can be set for each product group
You can also set different discount percentages by country code by adding a specific discount via the "Add country override" link

Unlinking a customer from a discount code

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 10:44:07 GMT

Unlinking a customer from a discount code

To unlink a customer from a discount code, simply press the red cross in the right column.

Linking a customer to a discount code

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 10:44:06 GMT

Linking a customer to a discount code

Open the desired discount code via the three dot menu >> edit. Then you can link the customer to the discount code using the blue link button.

Discount code

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 10:44:05 GMT

Discount code

In the automotive sector it is customary to work with fixed gross prices. The final price is ultimately determined by the discount. With the introduction of Discount Codes you can use a gross / net price structure.

Price list code

By linking the customer to a so-called price list code (discount code), a net price for a service is calculated with the set discount. This includes:

A specific discount percentage can be set for each product group
You can also set different discount percentages by country code by adding a specific discount via the "Add country override" link

Video tutorial

This video explains how to use the discount matrix found in your dashboard.

Managing your product catalog (V3)

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 09:48:02 GMT

Managing your product catalog (V3)

The management of your catalogue is done via the Jifeline Partner Dashboard.

Log in to your partner dashboard via https://partner.jifeline.com using your credentials
Select Products

There are 2 ways to configure a vehicle-product combination: 1) from the vehicle- or 2) products point of view.

1. After selecting a vehicle model, you are able to enable a product that is serviced, set a gross price and configure the outsource and insource settings.

2. After selecting a product, the vehicle can be enabled (+ gross price and outsource/insource settings).

Batch action

To provide a quick and easy option to fill your product catalogue, Jifeline provides a bulk action. This feature is only accessible form the products orientation (see above (2)).

Click "select multiple vehicles" on top of the vehicle section of the split screen,
Select the vehicle models
Click "bulk action" and set the gross price

4. Confirm action

Partner Guide - Product Catalog V3.pdf

Video tutorials

This video explains how to use the bulk action in the product catalogue.

This video explains how to import and export the product catalogue.

Employees

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 09:24:42 GMT

Employees

By clicking “employees” you can manage your employees and their role. Only operators and admin accounts can mutate tickets.

Four roles are available:

Senior Operator
Operator
Employee
Admin

Users in the role of Operator who actively participate in a ticket will be considered as an active user and will be calculated accordingly. Users in the Employee role are not charged.

Invoice debtor

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 09:24:41 GMT

Invoice debtor

We have created the invoice debtor. An invoice debtor is an umbrella organization over which the collective invoice flow may run. The invoice debtor in turn sends an invoice to an underlying debtor.

As an example we give a dealer which is linked to a dealer group. The dealer has a service performed. The service performed is invoiced to the dealer group, the invoice debtor. The dealer group in turn invoices the dealer.

Base client detail

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 09:24:40 GMT

Base client detail

On the base client detail page we find the following information:

General
General customer information such as name and reference
Registration date
Making a customer active or inactive
You can choose your clients locale
Group customers using a Branding Profile
Link your customer to a Price List Code
Set up an Invoice Debtor for this specific customer

Locations
Customer address information

Contact Points
Customer contact details (for both general and financial contact point)

Employees
Unique user name with which the customer can log into the Customer Portal
If necessary, you can send a password reset from this page to your customer

Financial
The currency used by the customer
Set up an Invoice Debtor for this specific customer
Link your customer to a Price List Code
Financial customer information such as IBAN and VAT number

Connector
Data of the OBD2 connectors assigned to the customer

Notes
Space for notes

Custom fields
Here you can add your own categories to display more customer information.

Base client list

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 02 May 2023 09:24:38 GMT

Base client list

Clients

By clicking “clients” you are able to manage your own customers.

>> list : a list with an overview of all clients (customers) appears

Click the “reference ID” and all client information will show up.

It is possible to search for a specific customer through various available filter options.

Once you have selected a client you can:

View or modify your clients data
Add (wifi) connectors to the clients record
Send a password reset

Diagnostic equipment

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:27:01 GMT

Diagnostic equipment

Before you can complete a ticket, the diagnostic device used must be registered.

Customer details

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:58 GMT

Customer details

In this section of the ticket workspace you will find the customer details.

Customer name
If the customer is using a J-ReX, you have the option of activating the sound actuator in the J-ReX via the alarm button behind the customer name
Phone number of the customer
The success rate of this customer's tickets
The branding associated with the customer

Customer name

Detailed customer information can be viewed by clicking on the customer name. Furthermore, here you can find the customer's contact details, location and recent tickets.

Product information

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:54 GMT

Product information

This window with information about the product can be found on the right side of the ticket detail page. In this window you can see which product or service the customer needs. Also the price and the total amount can be seen. The amount in brackets behind the product and price is the discount that is given over the product. Under “Add product” you can add a product if necessary by using the bar which says “search products”. Only products enabled for the vehicle of this ticket are shown here.

With the X mark behind the product you can remove the product from the ticket, it won’t be taken into account then. When pressing “Add product”, the window below pops up.

In this window there is a bar which says “add”, where you can chose a new or extra product. You can also see which products are already active on this ticket.

Discount

If you click on ''Additional discount'' underneath the product the following window appears.

This way you can add a discount to the product. You can add a reason if you want (not mandatory) and then enter the discount. You can either enter a percentage that gets subtracted from the product or enter the exact number you want to subtract from the price. You can’t enter both, you need to choose between a percentage or amount. When you enter a value in both boxes the application will choose just one and deletes the other one. To confirm the added discount you need to press “add”.

Remove

The red cross icon next to product can be used to remove a product from the list. This way it won’t be added to the total price.

Notes and attachments

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:52 GMT

Notes and attachments

We know how important it can be to keep track of all the details in your tickets.

In the Ticket Workspace, file upload can be used to attach relevant documents, images, or other files related to a customer issue or inquiry. This can include screenshots of error messages or any other files that might help a support agent better understand the issue and provide an appropriate resolution.

File upload via drag & drop
Or file explorer
Or paste a file from your clipboard (eg; a screenshot) in the note text area
Maximum file size is 25 MB

Pre- and post-scan

A pre- and post-diagnostic scan is a procedure that is performed on a vehicle prior to and after conducting a service. This process involves using specialized diagnostic tools to scan the vehicle's onboard computer systems for any error codes or faults that may indicate a problem with the vehicle.

The results of the scans can be uploaded to the ticket via drop-zones in the ticket notes area.

Share ticket notes

It is possible to share a note, including its attachments, with a client. A note can be shared with the customer via the Customer Portal. After a note is added in the Partner Portal, the operator is able to change the “public“ state of a note. When the note is made public, it will appear in the Customer Portal in the ticket history. The customer can download the attachment and read the note when the ticket has been completed.

In this way, you can, for example, make pre- and post-scan results and calibration certificates easily available to your customers.

Here is how it works for your customers:

Customer signs in to https://customers.obd.help
He or she opens the menu and select ticket history

3. Now the details of each ticket can be found

API documentation

The note and attachments are also available via the partner API. Please refer to our developer documentation for this.

In the video below you will see step by step how to add notes and attachments to a ticket.

Messenger

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:50 GMT

Messenger

Integrated messenger

The integrated messenger has everything you need in a chat app. Complete with features you need like file transfer, emoji, and more. You can manage the settings of the messenger in your partner dashboard.

The different features in the chat

Real-time messaging

We have turned our messenger app into a real-time messaging app, much like Whats App or Facebook Messenger. Complete with features you need like file transfer, emoji, and more.

One tab

In our messenger, both the operator and customer can use the feature 'one tab'. This feature allows you to answer a question asked with a single click of a button.

A request message

A request message allows the operator to ask the customer a question, which the customer can answer with one of the one tab answers. To activate this click to answer option, use the keyboard shortcut ctrl + 1, 2 or 3 depending on what you want to ask.

The question the operator asks in combination with the click to answer buttons is not fixed. This simply means that the one tab function is activated at the customer's chat.

With the click to answer option, you have 3 different options. These are as follows:

1. The thumb : If the operator asks the question in combination with the thumb, the customer will see the one tabs Yes and No.

2. The hashtag : If the operator asks the question in combination with the hashtag, the customer will see the one tabs 1, 2, 3, 4, 5.

3. The checkmark : If the operator asks the question in combination with the checkmark, the client will see the one tabs done and doesn't work

Once the customer responds to a click to answer button. It will always be linked as a reply to the question being asked. This way, there will be no confusion about which question is being answered as in the old chat application.

Multi-language user interface

The new chat messenger has built-in localization features that allow you to display the text (e.g. "Send") of the interfaces to the user in their own language.

Unread Message indicator

Unread Message Indicator: As an operator, you'll see an unread message indicator on the ticket summary card only if you're a participant in the chat for that specific ticket. This is a significant change from the previous chat application.

What this means: you won't see the unread message indicator for tickets you've pinned but haven't participated in the chat.

The indicator helps you prioritize tickets where you're directly involved in the conversation.

Type indicators

Real-time typing indicators help keep your users engaged.

Real time translations via DeepL

Our Messenger bridges the gap between technicians and clients, enabling seamless communication regardless of language. Mechanics and operators can easily set their preferred language within their respective portals – the Customer Portal and Partner Portal.

Vehicle and connection section

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:47 GMT

Vehicle and connection section

In the vehicle and connection section, the following data can be found:

The VIN number of the connected vehicle
Vehicle description
Terminal 30 and 15 information of the connected vehicle
Which remote is connected, how is it connected to the internet and what is its intenet latency?
Which local is connected and what is the internet latency?

VIN number

This is the VIN number of the connected vehicle. The VIN number is found either

Vehicle

This is the description in make, model, type of the connected vehicle. It is possible to change the model and type. For example, if the garage has selected the wrong vehicle.

OBD-II remote connector

To be able to remotely carry out work on a connected vehicle with the aid of a diagnostic device, an

OBD-II local connector must be added to the connection.

It is possible to use several OBD-II locals in one connection. An OBD-II local can also be removed from a connection. It is also possible to distinguish which of your colleagues is using a particular OBD-II local.

Profiles

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:42 GMT

Profiles

Under the Client Remote number in the ticket page you will find a OBD-II profile section. The profile selected is the default profile, which is used for the selected vehicle. If communication fails, it is possible that the used diagnostic tool does not use the normal OE protocol; then you need to try one of the other profiles. This can be selected by hit the small arow ↓ next to the profile name. Here you can select other profiles what may work for this car.

Explanation profiles

Plugin

A profile, specially made for a brand or family brand. That means that this plugin follows the OE standard protocol, and is dedicated to solve connection problems due to increased latency. It is important to wait until the scan is finished (100%). Communicating with the diagnostic tool during the scan will disturb the remote scan, and modules will be missing. These modules cannot be reached after the scan is 100%.

Best choice and when available the ‘default’ profile
Solves latency problems
Can be a problem when a diagnostic tool does not follow the OE standard protocol.

Smart

After starting the Smart scan, the remote “looks” at the actual data that is present at the diagnostic connector. The (mostly) irrelevant data will be blocked as, after the scan is finished, all “new” data will pass and “old” data will be blocked.

Forward

All car data communication, which is available at the diagnostic connector, will be transmitted via the Jifeline line. That means that also not relevant data will be transported and will absorb bandwidth. This is only a solution for cars with a diagnostic gateway.

When there is no Plugin or Smart Plugin available this could be a solution.
Works only on cars which are “quiet” on the diagnostic line.
Cars with a “busy” diagnostic line absorb bandwidth and can disturb the Jifeline connection.
Does not work when latency is high.

Forward+

As mentioned above, but now with a line filter. That means the addresses used for diagnoses are known and defined; only these addresses can be used for diagnostics. This is a better solution than “Forward”.

When there is no Plugin or Smart Plugin available, this could be a solution.
Works only on cars which are “quiet” on the diagnostic line.
Cars with a “busy” diagnostic line absorb bandwidth and can disturb the Jifeline connection.

DoIP (Diagnostics over Internet Protocol) / ENET

When There is a DoIP car connected to your dashboard and the customer has a Wifi-remote you are able to select the DoIP protocol.

DoIP is a protocol used in modern vehicles to perform diagnostic and maintenance tasks over the internet.

The protocol is based on the Internet Protocol (IP) and is designed to work over Ethernet networks. It enables faster communication speeds and greater bandwidth than traditional diagnostic protocols such as Controller Area Network (CAN) or K-Line.

Overall, the DoIP protocol is a crucial component of modern vehicle maintenance and diagnostics, and its use is likely to continue to expand as vehicles become even more advanced and connected.

DoIP uses UDS messages to communicate with the Electronic Control Units in a vehicle. UDS is a standardized diagnostic protocol that is also used on CAN-bus.

Vouchers

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:39 GMT

Vouchers

In the window with product information you can also find a bar available for vouchers. The customer can enter a voucher code when he creates the ticket. As operator you can also fill in this bar for a voucher.

Reference

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:34 GMT

Reference

This option can be found on the upper right corner. In this text bar you can change or adjust the reference. Mostly the customer uses it on the invoice. By entering a VIN or licence plate nr. they can trace the invoice to the car.

Closing or outsourcing tickets

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:31 GMT

Closing or outsourcing tickets

On the right top of the ticket detail page you will find the options to close the ticket that is being processed.

Complete

When the process has been completed successfully, you can press complete. This way you close the ticket.

Cancel

When you need to cancel a ticket you can use this button. When you cancel a ticket, the program will ask you to give a reason why.

Outsource ticket

When pressing on the button “outsource ticket” you can outsource your ticket. The ticket will then be sent to another operator from a Partner organisation. This can be useful in situation where the partner disposes of some software and you don’t.

Customer information

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:26 GMT

Customer information

In this window you will see information about the customer who created the ticket. You see general customer information such as telephone number and address. If the customer gives permission, the customer's current location can also be seen and you will see the most recent tickets.

If you click on the customer name, you will go directly to the customer in the dashboard.

Local and remote

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:24 GMT

Local and remote

The information about the local and remote that are connected to the ticket can be found on the top middle of the ticket detail page. You can find which remote and local are connected with their information behind it.

Remote

This bar shows which remote you are connected too. You can see the remote number and behind that are ping (connection speed),

Local

in this bar you are able to see the local that you are connected to. If you want to replace or add a local you can click on the local number.

Connection settings

When pressing the local number you will open a window where you can add, drop or replace a local. If you press replace local it will drop the attached local and replace it with the new one. If you hit ''Add" local this local will be added next to your current local.

You also have the option to drop the local from the connection by clicking ''Drop''.

Live data log

This toggle opens the live data log window in your tickets.

Ticket header

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:26:21 GMT

Ticket header

The ticket header contains the following:

Country of origin
Ticket ID
Information about the device the ticket was created on
Creation date and time, processing time
Operator working on the ticket
Complete button
Menu for additional ticket actions

Menu for additional ticket actions

Additional ticket actions are:

Pin ticket to side bar
Outsource the ticket to another service provider
Cancel the ticket
Check VIN on components
Show live log

Ticket list

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 14:25:55 GMT

Ticket list

Tickets

The ticket list contains all your historical tickets.

All actions performed by your customers and operators are summarized in the ticket history.
You can recall your previous jobs and dig into all the information like chat history or vehicle information.

Click the specific ticket number (“ID”), and all details on a specific ticket number will show up.

It is possible to search for a specific ticket through various available filter options. A ticket export can also be made.

Ticket listing

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 09:25:36 GMT

Ticket listing

In the ticket view, you will find an overview of all current and completed tickets. You will find a layout in tabs, namely Pending, In Progress, Outsourced and Finished. Furthermore, from this view you can activate the large-screen view .

Pending tickets

Pending tickets are tickets that have not yet been processed by the service center. This means that the technician in the garage is on hold, so to speak. You can accept the ticket by clicking on the join button.

In progress tickets

Outsourced tickets

This section contains an overview of the tickets that have been outsourced by your team to one of the other service providers.

Finished tickets

This tab contains all of today's completed tickets. Using the sorting options of the columns you can set the view to your personal preference.

Large-screen mode for monitoring and statistics

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 09:25:34 GMT

Large-screen mode for monitoring and statistics

Large-screen mode for monitoring and statistics can be activated by pressing this button.

It will then look like this:

Price lookup

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 09:25:32 GMT

Price lookup

Using the price lookup widget, you can easily look up a price of a service to be outsourced. After selecting:

the vehicle, via the VIN or manual selection
and the product to be outsourced

An overview is presented of service providers to which you can outsource the service.

Connectors

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 09:25:31 GMT

Connectors

In the header of the dashboard you will find two sections for the remote and local connectors. Additional information can be accessed for each connector here.

Under “Remotes” you will find the connected (online) remotes. Per Remote you can see what company owns the remote. When pressing on the button you open the window you see below. In this window you will find information about the vehicle it is connected too, information about the remote, information about the connection and information about the client.

Under “locals” you can find all the locals that are connected too your company server. With the button * you can rename your local. When you click the button > you get the information of that local.

Here you can see Hardware and software version and the time the local was connected to the server for the last time.

Close and open service center and schedule incoming tickets

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 09:25:29 GMT

Close and open service center and schedule incoming tickets

Close and open service center

This power button in the right top of the ticket dashboard can be used for closing, opening and scheduling the service center. The button “close service center” and “open service center” do what they say.

When the service center is closed a customer is unable to create a ticket. Tickets that are still being processed won’t be closed. The customer will get a message in his screen that the service center will open again the following day or after the weekend/holidays.

Scheduling tickets means that all the incoming tickets will have to wait until the scheduled time is over. When pressing “start scheduling incoming tickets” the window above pops up. Here you can enter for how long you are scheduling the incoming tickets. After that time tickets start coming in again. When a customer makes a ticket during the scheduled time, he will see when the service is available again. Until that time the customer has to wait. In the text bar “schedule message” you can enter a reason why you are scheduling incoming tickets. For example, coffee or lunchbreak.

Announcements

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Mon, 01 May 2023 09:25:28 GMT

Announcements

In the right upper corner of the partner dashboard you can find the changelog. If you press this the changelog window will open. You can see this window bellow. This will keep you up to date on all the changes that will be made to the dashboard. To make sure you don’t miss messages in the changelog, you can enter your email and the messages will also go to your mailbox. Updates that are shown in the changelog will be about improvements, bug-fixes and general announcements. Under every new message there is a text bar to give feedback or make a comment. You can also react by using an emoji.

Volkswagen AG platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:59:05 GMT

Volkswagen AG platform compability

Volkswagen AG is one of the biggest manufacturers in the automotive. All currently produced platforms by Volkswagen AG are compatible and shown in this section. Volkswagen AG produces cars from multiple brands: Audi, Bentley, Bugatti, Lamborghini, Porsche, SEAT, Škoda and Volkswagen.

*1 The transporter MK5 is equiped with both K-line and CAN, the MK6 uses only CAN

*2 No Specific Platform Name - Production plant owned together with Daimler AG

Toyota platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:59:03 GMT

Toyota platform compatibility

Toyota is one of the biggest manufacturers in the automotive. All currently produced platforms by Toyota are compatible and shown in this section. Toyota is an independent company. Lexus is a part of Toyota, and is being used for the comapnies luxery vehicles.

* No Specific Platform Name - Production plant was owned together with PSA GROUPE (Toyota took full ownership since March 2021)

Renault - Nissan - Mitsubishi Alliance platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:59:01 GMT

Renault - Nissan - Mitsubishi Alliance platform compatibility

Renault–Nissan–Mitsubishi Alliance is a large manufacturer in the automotive industry. All currently produced platforms by Renault–Nissan–Mitsubishi Alliance are compatible and shown in this section. Renault–Nissan–Mitsubishi Alliance produces cars from multiple brands: Renault, Nissan, Mitsubishi, Infiniti, Renault Samsung, Dacia, Alpine, Datsun, Venucia and Lada.

* Notice that Mercedes-Benz also uses this platform for their Citan, which is related to the Renault Kangoo

Hyundai motor company platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:59:00 GMT

Hyundai motor company platform compatibility

Hyundai motor Company is a large manufacturer in the automotive industry. In 2015 it bought a part of KIA to merge with the brand. All currently produced platforms by Hyundai motor Company are compatible and shown in this section. The company produces cars from two brands in Europe: Hyundai and KIA.

Honda motor company platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:58:57 GMT

Honda motor company platform compatibility

Honda Motor Company is a large manufacturer in the automotive industry. The company is not yet using a platform based strategy. This means the models that Honda produces are not related by a modulair used chassis. However they do use a lot of simular part in their vehicles. Which means the compability of the vehicles in not so different between the line-up. All currently compatible vehicles pruduced by Honda are shown in the section below.

*1 MK stands for which generation the vehicle is. (Example: Civic MK5 is a fifth generation Civic)

*2 Also known as Honda Fit

GROUPE PSA (stellantis) platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:58:56 GMT

GROUPE PSA (stellantis) platform compatibility

GROUPE PSA is one of the biggest manufacturers in the automotive. Since Januari 2021 the company has merged with FCA (Fiat Chrysler Automobiles). Together they are now producing vehicles under the name Stellantis. All currently produced platforms by GROUPE PSA are compatible and shown in this section. GROUPE PSA produces cars from multiple brands: Peugeot, Citroën, DS, Opel and Vauxhall.

*1 Opel Grandland X, Opel Vivano en Opel Combo use 3 high speed CANs (6&14 - 3&11 - 12&13)

*2 All vehicles use this profile except the Opel Grandland X, which uses PSA_GM Plugin

*3 No Specific Platform Name, Production plant was owned together with Toyota (Toyota took full ownership since March 2021)

Geely holding group platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:58:53 GMT

Geely holding group platform compatibility

Geely Holding Group is a large manufacturer in the automotive industry. In Europe it is mainly known for owning Volvo cars since 2010. Polestar and Lotus are also European brands owned by Geely Holding Group. In addition the company also owns a few Asian brands. All currently produced platforms by Geely Holding Group are compatible and shown in this section.

Ford motor company platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:58:34 GMT

Ford motor company platform compatibility

Ford Motor Company is a large manufacturer in the automotive industry. All currently produced platforms by Ford Motor Company are compatible and shown in this section. Ford Motor Company only owns one brand other than Ford: Lincoln. This brand only produces vehicles in the USA.

* No Specific Platform Name

Fiat Chrysler automobiles (Stellantis) platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:58:24 GMT

Fiat Chrysler automobiles (Stellantis) Platform Compatibility

Fiat Chrysler Automobiles is one of the biggest manufacturers in the automotive. Since Januari 2021 the company has merged with PSA GROUPE. Together they are now producing vehicles under the name Stellantis. All currently produced platforms by Fiat Chrysler Automobiles are compatible and shown in this section. Fiat Chrysler Automobiles produces cars from multiple brands: Abarth, Alfa Romeo, Chrysler, Dodge, Fiat, Fiat Professional, Jeep, Lancia, Maserati, and Ram Trucks.

*1 - High speed CAN

*2 - Low speed CAN

Daimler AG platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:58:16 GMT

Daimler AG platform compatibility

Daimler AG is a large manufacturer in the automotive industry. All currently produced platforms by Daimler AG are compatible and shown in this section. Daimler AG produces vehicles for two brands: Mercedes-Benz and Smart.

*1 - No Specific Platform Name - Production plant owned together with Volkswagen AG

*2 - Mercedes-Benz C-Class (W205 / S205). Mercedes-Benz C-Class (C205 / A205), Mercedes-Benz GLC-Class (X253 / C253), Mercedes-Benz E-Class (W213 / S213), Mercedes-Benz E-Class (C213 / A213), Mercedes-Benz E-Class (V213), Mercedes-Benz CLS-Class (C257), Mercedes-AMG GT 4-Door Coupé (X290), Mercedes-Benz S-Class (W223), Mercedes-Benz S-Class (V223), Mercedes-Maybach S-Class (Z223), Mercedes-Benz C-Class (W206)

*3 - Mercedes-Benz GLA-Class (H247), Mercedes-Benz GLB-Class (X247), Mercedes-Benz CLA-Class (C118), Mercedes-Benz A-Class (W177), Mercedes-Benz B-Class (W247), Mercedes-Benz EQA (250)

*4 - Mercedes-Benz G-Klasse (W463), Mercedes-Benz GLE-klasse (W167-V167-C167), Mercedes-Benz GLS-klasse (X167)

BMW group platform compatibility

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Fri, 28 Apr 2023 13:57:23 GMT

BMW group platform compatibility

BMW Group is a large manufacturer in the automotive industry. All currently produced platforms by BMW Group are compatible and shown in this section. BMW Group produces cars from multiple brands: BMW. Mini and Rolls-Royce.

Tips & Tricks Volkswagen

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:15 GMT

Tips & Tricks Volkswagen

Communication:

If there is canbus is in the car, there should be no problem communicating with the modules. Default profile is Plugin. If the total amount of modules exceeds 32 modules, please switch the profile to Forward.
If Kline is on the car, the module you want to connect to can be on a lot of different profiles and pins. We try to name them all, but if there is no description in the profile, please try until connection is made. For Kline profile choice, you can always relate to our document on Kline connection. This can be found here: HOW TO IDENTIFY KLINE PROTOCOL

If a particular module is found on a profile and is not named, please report to Jifeline so we can add it for you.

If a car has Kline (or a mix of canbus and kline), immobilizer functions with ODIS can only be performed if the engine control module and the Instrument panel are both on the same kline speed (if both are on the same obd socket pin).
For Crafters the profile for should be Forward to do key programming or ignition lock programming.
For Transporter V (7H) is kline until 2009, after 2009 it is canbus.

Other Tips and Tricks:

If there is no ignition status visible in ODIS with original interface (VAS 5054, VAS 6154), please switch the profile to Forward.
J2534 don’t show ignition status, this is a ODIS problem, not an Jifeline infrastructure issue.

Tips & Tricks Volvo

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:11 GMT

Tips & Tricks Volvo

Communication:

Communication is possible is Plugin if there are problems, please put it in Smart profile.

Other Tips and Tricks:

Aftermarket tow bars cannot be coded on a Volvo

Tips & Tricks VAG

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:09 GMT

Tips & Tricks VAG

Communication:

If there is canbus is in the car, there should be no problem communicating with the modules. Default profile is Plugin. If the total amount of modules exceeds 32 modules, please switch the profile to Forward.
If Kline is on the car, the module you want to connect to can be on a lot of different profiles and pins. We try to name them all, but if there is no description in the profile, please try until connection is made. For Kline profile choice, you can always relate to our document on Kline connection. This can be found here: https://docs.google.com/document/d/1o8NFNm9YS-6YrfdOaavphPNGCNUhu6LV/edit

If a particular module is found on a profile and is not named, please report to Jifeline so we can add it for you.

If a car has Kline (or a mix of canbus and kline), immobilizer functions with ODIS can only be performed if the engine control module and the Instrument panel are both on the same kline speed (if both are on the same obd socket pin).
For Crafters the profile for should be Forward to do key programming or ignition lock programming.
For Transporter V (7H) is kline until 2009, after 2009 it is canbus.

Tips & Tricks Toyota

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:08 GMT

Tips & Tricks Toyota

Communication:

Default profile: Toyota Can_smart is pin 6-14 canbus and includes 1 kline profile on pin 7.
Communication on Kline for toyota is for models up to 2006 not supported. There is no precieze model, but Yaris P9 and old Corolla’s are not supported.

Tips & Tricks Skoda

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:05 GMT

Tips & Tricks Skoda

Communication:

If there is canbus is in the car, there should be no problem communicating with the modules. Default profile is Plugin. If the total amount of modules exceeds 32 modules, please switch the profile to Forward.
If Kline is on the car, the module you want to connect to can be on a lot of different profiles and pins. We try to name them all, but if there is no description in the profile, please try until connection is made. For Kline profile choice, you can always relate to our document on Kline connection. This can be found here: HOW TO IDENTIFY KLINE PROTOCOL

If a particular module is found on a profile and is not named, please report to Jifeline so we can add it for you.

If a car has Kline (or a mix of canbus and kline), immobilizer functions with ODIS can only be performed if the engine control module and the Instrument panel are both on the same kline speed (if both are on the same obd socket pin).
For Crafters the profile for should be Forward to do key programming or ignition lock programming.
For Transporter V (7H) is kline until 2009, after 2009 it is canbus.

Other Tips and Tricks:

If there is no ignition status visible in ODIS with original interface (VAS 5054, VAS 6154), please switch the profile to Forward.
J2534 don’t show ignition status, this is a ODIS problem, not an Jifeline infrastructure issue.

Tips & Tricks Seat

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:03 GMT

Tips & Tricks Seat

Communication:

If there is canbus is in the car, there should be no problem communicating with the modules. Default profile is Plugin. If the total amount of modules exceeds 32 modules, please switch the profile to Forward.
If Kline is on the car, the module you want to connect to can be on a lot of different profiles and pins. We try to name them all, but if there is no description in the profile, please try until connection is made. For Kline profile choice, you can always relate to our document on Kline connection. This can be found here: HOW TO IDENTIFY KLINE PROTOCOL

If a particular module is found on a profile and is not named, please report to Jifeline so we can add it for you.

If a car has Kline (or a mix of canbus and kline), immobilizer functions with ODIS can only be performed if the engine control module and the Instrument panel are both on the same kline speed (if both are on the same obd socket pin).
For Crafters the profile for should be Forward to do key programming or ignition lock programming.
For Transporter V (7H) is kline until 2009, after 2009 it is canbus.

Other Tips and Tricks:

If there is no ignition status visible in ODIS with original interface (VAS 5054, VAS 6154), please switch the profile to Forward.
J2534 don’t show ignition status, this is a ODIS problem, not an Jifeline infrastructure issue.

Tips & Tricks Renault

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:01 GMT

Tips & Tricks Renault

Communication:

On the newer Renault vehicles, when using the Clip (original equipment), the engine will not be found. Please switch the profile to smart.
When using Immo-tool for renault, profile needs to be in smart of Forward.

Tips & Tricks PSA

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:54:00 GMT

Tips & Tricks PSA

Communication:

Default profile is Plugin. High speed canbus on pins 6/14 and 3/8.
If the engine code is a 9HR type, there will be no communication possible with the engine controller.
On (Can) models with a diesel engine and there is no communication with the additief module (but the customer can read out fine), please switch the smart profile, than there will be communication.
Model 307 can be Canbus or Kline. If the OBD socket is left of the steering wheel it is a Kline (before 2005). If the socket is in front of the shift lever, it is a canbus vehicle (2005 -).

Other Tips and Tricks:

Pin extraction for PSA can only be done by Jifeline on can-bus vehicles with a working key available. Kline is not supported for pin extraction.
For use of the original PSA tool (Diagbox), the profile needs to be in smart, otherwise there will be no automatic VIN detection. After that the profile can be put in Plugin again for better connection. Also manual input of the vin can overcome this problem.
If working on keyless vehicles, the key must be in the override position, otherwise dtc’s cannot be cleared or programming cannot be performed.

Tips & Tricks Peugeot

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:58 GMT

Tips & Tricks Peugeot

Communication:

Default profile is Plugin. High speed canbus on pins 6/14 and 3/8.
If the engine code is a 9HR/9HD type, there will be no communication possible with the engine controller.
On (Can) models with a diesel engine and there is no communication with the additief module (but the customer can read out fine), please switch the smart profile, than there will be communication.
Model 307 can be Canbus or Kline. If the OBD socket is left of the steering wheel it is a Kline (before 2005). If the socket is in front of the shift lever, it is a canbus vehicle (2005 -).

Other Tips and Tricks:

Pin extraction for PSA can only be done by Jifeline on can-bus vehicles with a working key available. Kline is not supported for pin extraction.
For use of the original PSA tool (Diagbox), the profile needs to be in smart, otherwise there will be no automatic VIN detection. After that the profile can be put in Plugin again for better connection. Also manual input of the vin can overcome this problem.
If working on keyless vehicles, the key must be in the override position, otherwise dtc’s cannot be cleared or programming cannot be performed.
Fault code B1003 is a phantom fault and can not be solved.

Tips & Tricks Opel

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:57 GMT

Tips & Tricks Opel

Communication:

If you are using GDS or SPS on Opel vehicles, please set the profile to SMART. Wait for the scan to finish and proceed as normal. Please do not connect a tool during SMART scanning.
For Kline Opel cars, be aware that there are more than one profile to select. The modules are listed in the profile.
For Opels based on PSA platform, a lot of tools do not use the right pin settings. They try on pin 3 and 8, but on these vehicles the pinning is pin 3 and 11 (The Plugin profile has these settings) To overcome this problem please put a breakout box in between and connect pin 8 to 11 with a jumper wire. This problem is already seen in the original SPS program, this is not a Jifeline Networks problem.

Tips & Tricks Nissan

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:51 GMT

Tips & Tricks Nissan

Communication:

Default profile is Combi Nissan Can_Smart_K_FST_ECM. This is with Canbus on pin 6/14 and kline on pin 7.

Other Tips and Tricks:

For key programming on J10 keyless keys, the keys are hard to program. This is because of the fact there is a microswitch in the ignition lock which fails, so the key-in status on cannot be detected. This will result in a non starting car, as the key needs to be detected before it can be learned and all keys are always cleared before learning, So please check in livedata first if the key in status is detected. The keyless part is also hard to be detected. You will have to keep pressing the button on the remote in a 1 sec frequentie (when the tool tells you to push) until it is recognized. Only if the key is programmed, the remote can be programmed.

Tips & Tricks Mercedes

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:48 GMT

Tips & Tricks Mercedes

Communication:

Default Profile: Forward+ canbus on pin 6/14

For good communication with Mercedes the connection needs to be under 100 ms.
Sprinters before 2013 have trouble connecting with ABS modules. If there is no connection in smart or Forward +, there is no way of connecting in the current infrastructure.
Kline Mercedes (W639 before 2008 for example) is not supported. There is a Kline profile , but this is experimental.
There are known issues with connecting to older Mercedes types (W204, W245, W169). The customer can read out the car with no problem, but cannot be done via remote. If the connection on the obd plug is correct and the car is running and there is still no response from the car (this also can be seen in the log), than there is no way of communicating with the car, because of Kline profile which is not supported at the moment.

Tips & Tricks Lancia

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:46 GMT

Tips & Tricks Lancia

Communication:

The Can profile is very important on Fiat based vehicles. There can be 3 variant: 50 kb, 250 kb and 500kb. Basic rule is that if a vin is read out automatically by the reader, the profile is always 500kb. If it is not it can be 50kb or 250kb (or still 500kb, but ignition was not on when remote was connected). To check; open the log and turn ignition on. Switch profile to 50kb Forward. If there are can-messages visible in the log, the connection speed is 50kb. Same trick can be used for 250 kb. If the bitrate is 50kb or 250kb, the car has also Kline (engine on pin 7).
If there is no communication in Plugin with the radio module on newer Fiats, the profile should be put in smart. We are working on the plugin to support the Radio as well, but for the time being, smart is the only option.
Fiat (and chrysler) started using Security Gateways in the models Fiat 500, Doblo and Dodge RAM. You can only read these cars and cannot do any other actions on these cars. You will need original tool to do functions (clear codes etc) on these cars.

Other Tips and Tricks:

For key programming, make sure ALL keys are present and programmed in one session. If a key is forgotten (is at the customers for example), this key will be blacklisted and can not be used ever again.
Save extraction of pincode on 50kb and 500kb Fiats can be done by Jifeline.

Tips & Tricks Jeep

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:43 GMT

Tips & Tricks Jeep

Communication:

The Can profile is very important on Fiat based vehicles. There can be 3 variant: 50 kb, 250 kb and 500kb. Basic rule is that if a vin is read out automatically by the reader, the profile is always 500kb. If it is not it can be 50kb or 250kb (or still 500kb, but ignition was not on when remote was connected). To check; open the log and turn ignition on. Switch profile to 50kb Forward. If there are can-messages visible in the log, the connection speed is 50kb. Same trick can be used for 250 kb. If the bitrate is 50kb or 250kb, the car has also Kline (engine on pin 7).
If there is no communication in Plugin with the radio module on newer Fiats, the profile should be put in smart. We are working on the plugin to support the Radio as well, but for the time being, smart is the only option.
Fiat (and chrysler) started using Security Gateways in the models Fiat 500, Doblo and Dodge RAM. You can only read these cars and cannot do any other actions on these cars. You will need original tool to do functions (clear codes etc) on these cars.
When using the original Tool (WITECH), use smart, but scan the car without the tool connected, otherwise comms will be difficult.

Tips & Tricks Iveco

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:42 GMT

Tips & Tricks Iveco

Communication:

The Can profile is very important on Fiat based vehicles. There can be 3 variant: 50 kb, 250 kb and 500kb. Basic rule is that if a vin is read out automatically by the reader, the profile is always 500kb. If it is not it can be 50kb or 250kb (or still 500kb, but ignition was not on when remote was connected). To check; open the log and turn ignition on. Switch profile to 50kb Forward. If there are can-messages visible in the log, the connection speed is 50kb. Same trick can be used for 250 kb. If the bitrate is 50kb or 250kb, the car has also Kline (engine on pin 7).
If there is no communication in Plugin with the radio module on newer Fiats, the profile should be put in smart. We are working on the plugin to support the Radio as well, but for the time being, smart is the only option.
Fiat (and chrysler) started using Security Gateways in the models Fiat 500, Doblo and Dodge RAM. You can only read these cars and cannot do any other actions on these cars. You will need original tool to do functions (clear codes etc) on these cars.

Other Tips and Tricks:

For key programming, make sure ALL keys are present and programmed in one session. If a key is forgotten (is at the customers for example), this key will be blacklisted and can not be used ever again.
Save extraction of pincode on 50kb and 500kb Fiats can be done by Jifeline.

Tips & Tricks Honda

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:41 GMT

Tips & Tricks Honda

Communication:

For key programming, no profile is defined and cannot be done with the current infrastructure.

Tips & Tricks Ford

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:38 GMT

Tips & Tricks Ford

Communication:

there are 2 profile settings (HS and HS2) in the basics the new cars are HS2 and old cars are HS. List from HS 2 vehicles:

Fiesta 7
Kuga 3
Focus 4
Mondeo 5
Newer transit from 2.0 ecoblue engines
Newer Eco sports from half 2018*
Newer transit connects from half 2018*

If the remote goes offline during the scan at approx. 75% of the scan, than it is a high speed 2 car being scanned on the High speed Plugin. The customer needs to replug the remote and the profile needs to be changed.
Older cars with the Engine Control Module on the J1835 profile are not supported.

Other Tips and Tricks:

There needs to be 2 keys programmed to start a Ford. So if the BCM is replaced, please make sure the customer has 2 keys available.

Tips & Tricks Fiat

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:37 GMT

Tips & tricks Fiat

Communication:

The Can profile is very important on Fiat based vehicles. There can be 3 variant: 50 kb, 250 kb and 500kb. Basic rule is that if a vin is read out automatically by the reader, the profile is always 500kb. If it is not it can be 50kb or 250kb (or still 500kb, but ignition was not on when remote was connected). To check; open the log and turn ignition on. Switch profile to 50kb Forward. If there are can-messages visible in the log, the connection speed is 50kb. Same trick can be used for 250 kb. If the bitrate is 50kb or 250kb, the car has also Kline (engine on pin 7).
Fiat based cars are using Security Gateways in all models. You can only read these cars and cannot do any other actions on these cars. You will need original tool to do functions (clear codes etc) on these cars.

Other Tips and Tricks:

For key programming, make sure ALL keys are present and programmed in one session. If a key is forgotten (is at the customers for example), this key will be blacklisted and can not be used ever again.
Save extraction of pincode, on 500kb Fiats can be done by Jifeline.

Tips & Tricks DS

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:35 GMT

Tips & Tricks DS

Communication:

Default profile is Plugin. High speed canbus on pins 6/14 and 3/8.
If the engine code is a 9HR type, there will be no communication possible with the engine controller.
On (Can) models with a diesel engine and there is no communication with the additief module (but the customer can read out fine), please switch the smart profile, than there will be communication.
Model 307 can be Canbus or Kline. If the OBD socket is left of the steering wheel it is a Kline (before 2005). If the socket is in front of the shift lever, it is a canbus vehicle (2005 -).

Other Tips and Tricks:

Pin extraction for PSA can only be done by Jifeline on can-bus vehicles with a working key available. Kline is not supported for pin extraction.
For use of the original PSA tool (Diagbox), the profile needs to be in smart, otherwise there will be no automatic VIN detection. After that the profile can be put in Plugin again for better connection. Also manual input of the vin can overcome this problem.
If working on keyless vehicles, the key must be in the override position, otherwise dtc’s cannot be cleared or programming cannot be performed.

Tips & Tricks Dacia

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:34 GMT

Tips & Tricks Dacia

Communication:

On the newer Renault/Dacia vehicles, when using the Clip (original equipment), the engine will not be found. Please switch the profile to smart.
When using Immo-tool for renault, profile needs to be in smart of Forward.

Tips & Tricks Citroën

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:32 GMT

Tips & Tricks Citroën

Communication:

Default profile is Plugin. High speed canbus on pins 6/14 and 3/8.
If the engine code is a 9HR type, there will be no communication possible with the engine controller.
On (Can) models with a diesel engine and there is no communication with the additief module (but the customer can read out fine), please switch the smart profile, than there will be communication.
Model 307 can be Canbus or Kline. If the OBD socket is left of the steering wheel it is a Kline (before 2005). If the socket is in front of the shift lever, it is a canbus vehicle (2005 -).

Other Tips and Tricks:

Pin extraction for PSA can only be done by Jifeline on can-bus vehicles with a working key available. Kline is not supported for pin extraction.
For use of the original PSA tool (Diagbox), the profile needs to be in smart, otherwise there will be no automatic VIN detection. After that the profile can be put in Plugin again for better connection. Also manual input of the vin can overcome this problem.
If working on keyless vehicles, the key must be in the override position, otherwise dtc’s cannot be cleared or programming cannot be performed.

Tips & Tricks BMW

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 11:53:30 GMT

Tips & Tricks BMW

Communication:

Bmw is supported from 2007-8 month and up. Older models are not supported for remote diagnostic.
Working with the original software (ISTA) please put the profile in forward. Otherwise the ignition (PAD) status will not be recognized.
Use of the original ICOM tool with Ista Next for coding/programming is not possible. This because of Doip (Ethernet) check, which is not yet supported by the Jifeline remote interface.

Other Tips and Tricks:

Coding can be done on BMW with BMW explorer and AutoHex II.
Keys for BMW dont need programming, they should work right away. Keyless keys can be activated by tool.

Tips & Tricks Audi

frank@jifeline.com (Jifeline Remote Diagnostics en Networks) — Tue, 25 Apr 2023 07:46:25 GMT

Tips & Tricks Audi

Communication:

If there is canbus is in the car, there should be no problem communicating with the modules. Default profile is Plugin. If the total amount of modules exceeds 32 modules, please switch the profile to Forward.
If Kline is on the car, the module you want to connect to can be on a lot of different profiles and pins. We try to name them all, but if there is no description in the profile,
please try until connection is made. For Kline profile choice, you can always relate to our document on Kline connection. This can be found here: HOW TO IDENTIFY KLINE PROTOCOL

If a particular module is found on a profile and is not named, please report to Jifeline so we can add it for you.

If a car has Kline (or a mix of canbus and kline), immobilizer functions with ODIS can only be performed if the engine control module and the Instrument panel are both on the same kline speed (if both are on the same obd socket pin).
For Crafters the profile for should be Forward to do key programming or ignition lock programming.
For Transporter V (7H) is kline until 2009, after 2009 it is canbus.

Other Tips and Tricks:

If there is no ignition status visible in ODIS with original interface (VAS 5054, VAS 6154), please switch the profile to Forward.
J2534 don’t show ignition status, this is a ODIS problem, not an Jifeline infrastructure issue.

jifeline-partner-portal

Images for commercial use

Images for commercial use

Outsourced-Notes

Outsourced-Notes

Notes and attachments also allows you to save notes on an insourced ticket that becomes visible to the service provider that outsourced the ticket.

This functionality can work with all types of notes such as photos, videos, documents and text.

In the following example, a ticket was sent from service provider A to B.

Service provider B saves a note on the ticket and sets the note to public(see picture below).

UDS protocol guide

UDS protocol guide

Example 1: request extend diagnostic session ﻿

Request message

Positive response message

Negative response message

Request message

Response message

Example 3: requesting vehicle-manufacturer-specific ECU hardware number (serial number)

Request message

Response message

Example 4: Programming date when ECU was last programmed ﻿

Request message

Response message

Example 5: check if tester is present. (i.e. check if remote is still connected to CAN-bus)

Request message

No response message

Live data log

Live data log

Transponder key programming for Toyota Aygo I & II based vehicle models

Transponder Key Programming for Toyota Aygo I & II based vehicle models ﻿

Transponder key programming for Renault KWP2000 vehicle models

Transponder key programming for Renault KWP2000 vehicle models

Transponder key programming for Renault K-line vehicle models

Transponder key programming for Renault K-line vehicle models

Transponder key programming for PSA vehicles (BSI)

Transponder key programming for PSA vehicles (BSI)

Transponder key programming for Opel vehicles (GMLan)

Transponder key programming for Opel vehicles (GMLan)

Transponder key programming for Hyundai / Kia vehicles

Transponder key programming for Hyundai / Kia vehicles ﻿

Transponder key programming for Fiat

Transponder key programming for Fiat

VAG automated towbar coding

VAG automated towbar coding

PSA automated towbar coding

PSA automated towbar coding

Mercedes-Benz automated towbar coding

Mercedes-Benz automated towbar coding ﻿

Ford automated towbar coding

Ford automated towbar coding

How to setup automated functions

How to setup automated functions

Expose product price list as REST API

Expose product price list as REST API

Partner admin API

Partner admin API

Wifi router TCP / UDP settings

Wifi router TCP / UDP settings

TCP / UDP settings

Test the portscan in a browser

Wifi netwerk security ﻿

Host ﻿

Network Band ﻿

OTA firmware update

OTA firmware update

Connecting the OBD-II local

Connecting the OBD-II local ﻿

How to connect the wireless remote to a workshop’s 2.4 GHz WiFi network?

How to connect the wireless remote to a workshop’s 2.4 GHz WiFi network?

How to link a (wireless) remote to a client?

How to link a (wireless) remote to a client?

Creating a ticket using a wireless remote

Creating a ticket using a wireless remote

Preferred currency

Preferred currency

Setting up insource / outsource relationships

Setting up insource / outsource relationships

Setting-up an insource / outsource relationship ﻿

Outsource settings

Outsource settings

Example 1: request extend diagnostic session

Example 4: Programming date when ECU was last programmed

Transponder Key Programming for Toyota Aygo I & II based vehicle models

Transponder key programming for Hyundai / Kia vehicles

Mercedes-Benz automated towbar coding

Wifi netwerk security

Host

Network Band

Connecting the OBD-II local

Setting-up an insource / outsource relationship

Manage "auto-closing" of tickets

Remote Acces URL

Help Center URL

Connector registration

Product information

Notes and attachments