Kiwi 3 with 2003 Toyota MR2

Help on issues you run into with LapTimer; in case you have a question on how to use LapTimer, use the forum "Using LapTimer" instead
cyaniccypher
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 9
Joined: Sun Sep 18, 2016 12:48 am

Kiwi 3 with 2003 Toyota MR2

Post by cyaniccypher » Sun Sep 18, 2016 12:51 am

When looking at system status it keeps saying for my car: "OBD Data Rate" in red and "The OBD Sensor does not receive data at an expected rate"

I have tried this:
Please add the following string to LapTimer ‣ Administration ‣ Settings ‣ Expert Settings ‣ OBD Tweaks / Exclude PIDs:

Code:
0900092009400902
It did not work.

Anything else that I need to do?
User avatar
Harry
Site Admin
Site Admin
Posts: 9077
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Kiwi 3 with 2003 Toyota MR2

Post by Harry » Sun Sep 18, 2016 9:09 am

Please do not exclude PIDs except when knowing exactly what the problem is. The forum is full of make / model / year specific issues and work arounds and you can just copy them. I assume the Toyota does not have a CAN bus, so the rate will never be very high. The error message however means, there is some communication issue. You may follow the FAQ on "Debugging OBD connections".

- Harry
Image Image Image Image
cyaniccypher
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 9
Joined: Sun Sep 18, 2016 12:48 am

Re: Kiwi 3 with 2003 Toyota MR2

Post by cyaniccypher » Sun Sep 18, 2016 12:54 pm

Harry wrote:Please do not exclude PIDs except when knowing exactly what the problem is. The forum is full of make / model / year specific issues and work arounds and you can just copy them. I assume the Toyota does not have a CAN bus, so the rate will never be very high. The error message however means, there is some communication issue. You may follow the FAQ on "Debugging OBD connections".

- Harry
I followed the instructions and send you the logs.
User avatar
Harry
Site Admin
Site Admin
Posts: 9077
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Kiwi 3 with 2003 Toyota MR2

Post by Harry » Mon Sep 19, 2016 10:35 am

The logs show you have 2 ECUs answering most request. Reply are slow, but in the expected range. The replies delivered are often inconsistent, so you will probably see artifacts in data. LapTimer has no filtering capabilities for certain ECUs currently, this would allow removing one of them and both speed up communication and get better data. Maybe in v21...

You may try switching Settings ‣ Expert Settings ‣ OBD Tweaks / Adaptive Timing from Optimized to Enabled - maybe you get better results here.

- Harry
Image Image Image Image
cyaniccypher
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 9
Joined: Sun Sep 18, 2016 12:48 am

Re: Kiwi 3 with 2003 Toyota MR2

Post by cyaniccypher » Tue Sep 20, 2016 12:31 am

Harry wrote:The logs show you have 2 ECUs answering most request. Reply are slow, but in the expected range. The replies delivered are often inconsistent, so you will probably see artifacts in data. LapTimer has no filtering capabilities for certain ECUs currency, this would allow removing one of them and both speed up communication and get better data. Maybe in v21...

You may try switching Settings ‣ Expert Settings ‣ OBD Tweaks / Adaptive Timing from Optimized to Enabled - maybe you get better results here.

- Harry
My MR2 has the SMT transmission which has it's own computer that must be the second ECU that is being picked up.

How likely are you to make a fix for this in V21 and how soon would that be?

Next time I go out I will try the adaptive timing setting and let you know how it worked out.
User avatar
Harry
Site Admin
Site Admin
Posts: 9077
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Kiwi 3 with 2003 Toyota MR2

Post by Harry » Tue Sep 20, 2016 9:52 pm

v21 is the Spring 2017 release. This is considered a feature by the way, not fix (as it is working even for this non standard situation).

- Harry
Image Image Image Image
cyaniccypher
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 9
Joined: Sun Sep 18, 2016 12:48 am

Re: Kiwi 3 with 2003 Toyota MR2

Post by cyaniccypher » Thu Apr 20, 2017 3:48 pm

Harry wrote:v21 is the Spring 2017 release. This is considered a feature by the way, not fix (as it is working even for this non standard situation).

- Harry
Was this implemented?
User avatar
Harry
Site Admin
Site Admin
Posts: 9077
Joined: Sun Sep 12, 2010 10:32 am
Location: Siegum, Germany
Contact:

Re: Kiwi 3 with 2003 Toyota MR2

Post by Harry » Thu Apr 20, 2017 7:14 pm

I have changed plans for development in the sensors area in general. I plan to provide a scriptable interface for sensors later this year. Instead of building features into LapTimer addressing very special requirements, this will allow users to change integration and data handling on their own. Not committed yet, but excited to work on it! :-)

- Harry
Image Image Image Image
cyaniccypher
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 9
Joined: Sun Sep 18, 2016 12:48 am

Re: Kiwi 3 with 2003 Toyota MR2

Post by cyaniccypher » Mon Jun 19, 2017 12:36 am

Any update on this? Today I had an event and when I did the overlayed video the engine RPM and the video are clearly out of sync.
cyaniccypher
Fewer than 10 Posts
Fewer than 10 Posts
Posts: 9
Joined: Sun Sep 18, 2016 12:48 am

Re: Kiwi 3 with 2003 Toyota MR2

Post by cyaniccypher » Mon Sep 25, 2017 7:21 pm

Harry wrote:I have changed plans for development in the sensors area in general. I plan to provide a scriptable interface for sensors later this year. Instead of building features into LapTimer addressing very special requirements, this will allow users to change integration and data handling on their own. Not committed yet, but excited to work on it! :-)

- Harry
Any update?
Post Reply