Torque

Forums

Forums

Guest  

Show or hide header
Welcome Guest, posting in this forum require registration.




Torque » Torque OBD ECU Scanner » Torque Discussion / Ideas » What is this "1" in the end?

Pages: [1]
Author Topic: What is this "1" in the end?
Makarov
Member
Posts: 5
Post What is this "1" in the end?
on: August 21, 2017 (GMT)

So, I got a communications log between TP and my device:
there are two types of requests from TP: 010D and 010D1

>010D1
410D04
>010D1
410D04
>010D1
410D05
>010D1
410D05
>010D1
410D05
>010D1
410D06
>010D1
410D06
>010D1
410D07
>010D1
410D07
>010D1
410D08
>010D1
410D08
>010D1
410D08
>010D1
410D09
>010D1
410D09
>010D1
410D0A
>010D1
410D0A
>010D1
410D0B
>010D1
410D0B
>010D1
410D0C
>010D1
410D0C
>010D1
410D0D
>010D1
410D0D
>010D1
410D0E
>010D1
410D0E
>010D1
410D0F
>010D1
410D0F
>010D1
410D10
>010D1
410D10
>010D1
410D11
>010D1
410D11
>010D1
410D11
>010D1
410D12
>010D1
410D12
>010D1
410D12
>010D1
410D13
>010D
410D13
>010D
410D15
>010D
410D17
>010D
410D19
>010D
410D1B
>010D
410D1D
>010D
410D1F
>010D
410D21
>010D
410D23
>010D
410D25
>010D
410D27
>010D
410D29
>010D
410D2B
>010D
410D2D
>010D
410D2F
>010D
410D31
>010D1
410D33
>010D1
410D34
>010D1
410D34
>010D1
410D35
>010D1
410D35
>010D1
410D36
>010D1
410D37
>010D1
410D37
>010D1
410D37
>010D1
410D38
>010D1
410D38
>010D1
410D38
>010D1
410D39
>010D1
410D39
>010D1
410D3A
>010D1
410D3A
>010D1
410D3B
>010D1
410D3B
>010D1
410D3B
>010D1
410D3C
>010D1
410D3C
>010D1
410D3D
>010D1
410D3D
>010D1
410D3E
>010D1
410D3E
>010D1
410D3F
>010D1
410D3F
>010D1
410D40
>010D1
410D40
>010D1
410D41
>010D1
410D41
>010D1
410D41
>010D1
410D42
>010D1
410D42
>010D1
410D43
>010D1
410D43
>010D1
410D44
>010D1
410D44
>010D1
410D44
>010D1
410D45
>010D
410D45
>010D
410D47
>010D
410D49
>010D
410D4B
>010D
410D4D
>010D
410D4F
>010D
410D51
>010D
410D53
>010D
410D55
>010D
410D57
>010D
410D59
>010D
410D5B
>010D
410D5D
>010D
410D5F
>010D
410D61
>

the response is the internal timer, which clock is 0,1 s
As you can see, 010D1 requests are much faster than 010D’s. While communicating with my device, TP changes this speed automatically. Does anyone know, why requests are different? Also, custom PID’s requests are always sent without “1” in the end, so they slow down the communication.

Capp777
Member
Posts: 2744
Post Re: What is this "1" in the end?
on: August 21, 2017 (GMT)

Not seeing the timer numbers you
mentioned but I believe one form of
the command is eliminating a timeout
waiting period for additional messages
while the other times out before
returning.

As always I could be wrong.

(Just another Torque Pro user).

cintakc
Member
Posts: 1366
Post Re: What is this "1" in the end?
on: August 22, 2017 (GMT)

DSheets_ELM327DS.

There is a way to speed up the retrieval of
information, if you know how many responses will be
sent. By telling the ELM327 how many lines of data to
receive, it knows when it is finished, so does not have
to go through the final timeout, waiting for data that is
not coming. Simply add a single hex digit after the
OBD request bytes – the value of the digit providing the
maximum number of responses to obtain, and the
ELM327 does the rest. For example, if you know that
there is only one response coming for the engine
temperature request that was previously discussed,
you can send:
>01 05 1
and the ELM327 will return immediately after obtaining
only one response. This may save a considerable
amount of time, as the default time for the AT ST timer
is 200 msec. (The ELM327 still sets the timer after
sending the request, but that is only in case the single
response does not arrive.)

Makarov
Member
Posts: 5
Post Re: What is this "1" in the end?
on: August 22, 2017 (GMT)

Thank you so much) I didnt read datasheet carefully.
Hmm… OK, but this does not explain why TP changes the way it generates a request.

Here:

>010D1
410D12 //1,2s
>010D1
410D12 //1,2s
>010D1
410D13 //1,3s
>010D
410D13 //1,3s
>010D
410D15 //1,5s
>010D
410D17 //1,7s
>010D
410D19

I can see that everything goes ok with fast requests (delay is less than 0,1s = 2-3 readings per 0,1s) and then something happens and TP gets back to slow requests.
1) Maybe there is a delay in TP which resets this mode? And if so, what kind is this delay? Delay between TP request and the answer?
2) Or maybe this is because there are lost messages (on bluetooth channel, which I cant sniff)

Pages: [1]
WP-Forum by: Fredrik Fahlstad, Version: 2.4
Page loaded in: 0.099 seconds.

  Follow me on twitter