Pages: [1]
Author Topic: Possible to display curent gear via ELM327?  (Read 5858 times)
BlackT
Hero Member
*****

Karma: +79/-39
Offline Offline

Posts: 1421



« on: June 11, 2020, 08:07:40 AM »

Does anyone have some info about this. Is it possible to display curent gear with elm327, on program like tourqeapp?
Logged
Lechuga
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 41


« Reply #1 on: June 12, 2020, 12:29:14 AM »

Gangi is not available to OBDII protocol. You could however define a formula that, based on engine and vehicle speeds, could infer which gear you are in, which is similar to what I believe the ME7 does.

I read somewhere that Torque currently has experimental support for different types of adapters, one being specific for ME7 and requiring some configuration similar to the .ecu files.
Logged
H2Deetoo
Sr. Member
****

Karma: +26/-1
Offline Offline

Posts: 256


« Reply #2 on: June 12, 2020, 12:55:40 AM »

Recently i placed a cluster which was wrongly configured, it had a wrong wheel diameter constant in eeprom.
Besides the shown speed being greatly mismatched, it also showed wrong gear indication.

So this means it indeed calculates the gear index based on speed, rpm, wheel rotations etc.


Regards,
H2Deetoo
Logged
BlackT
Hero Member
*****

Karma: +79/-39
Offline Offline

Posts: 1421



« Reply #3 on: June 12, 2020, 01:46:25 AM »

ME7 have curent gear output in vcds blocks.
I don't know are the PIDs that elm reads same as vcds blocks.

I would like to read it direct from trans/ecu. But I am also okay with option to calculate it from rpm and speed. Yust I don't know how to make that display on torque pro( or some other app)
Didn't find anywhere how to set that formula to read two PIDs and calculate something from them
Logged
Lechuga
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 41


« Reply #4 on: June 15, 2020, 12:26:59 AM »

I have an idea how to do it in Torque.

First define custom PIDs for each gear based on gear ratio, rpm and speed as follows (using my gear ratios from a Audi TT 8n 6sp manual with 225x40r18 wheels):
1st: val{Engine RPM}*0.008367364/val{Speed (ODB)}
2nd: val{Engine RPM}*0.013579534/val{Speed (ODB)}
3rd: val{Engine RPM}*0.02125811/val{Speed (ODB)}
4th: val{Engine RPM}*0.026270507/val{Speed (ODB)}
5th: val{Engine RPM}*0.033016907/val{Speed (ODB)}
6th: val{Engine RPM}*0.039716487/val{Speed (ODB)}

And the magic comes in the following custom PID:
Gangi: CLOSEST(1:1:val{1st}=1:val{2nd}=2:val{3rd}=3:val{4th}=4:val{5th}=5:val{6th}=6)

Untested in a live scenario but it works in a test environment. Naturally you can put each individual gear calculation into the gangi PID but I split them up for ease of understanding
Logged
BlackT
Hero Member
*****

Karma: +79/-39
Offline Offline

Posts: 1421



« Reply #5 on: June 15, 2020, 04:09:27 AM »

I have an idea how to do it in Torque.

First define custom PIDs for each gear based on gear ratio, rpm and speed as follows (using my gear ratios from a Audi TT 8n 6sp manual with 225x40r18 wheels):
1st: val{Engine RPM}*0.008367364/val{Speed (ODB)}
2nd: val{Engine RPM}*0.013579534/val{Speed (ODB)}
3rd: val{Engine RPM}*0.02125811/val{Speed (ODB)}
4th: val{Engine RPM}*0.026270507/val{Speed (ODB)}
5th: val{Engine RPM}*0.033016907/val{Speed (ODB)}
6th: val{Engine RPM}*0.039716487/val{Speed (ODB)}

And the magic comes in the following custom PID:
Gangi: CLOSEST(1:1:val{1st}=1:val{2nd}=2:val{3rd}=3:val{4th}=4:val{5th}=5:val{6th}=6)

Untested in a live scenario but it works in a test environment. Naturally you can put each individual gear calculation into the gangi PID but I split them up for ease of understanding
Thanks man,
Do you have screenshot how this PID looks like  in Toruqe
Logged
BlackT
Hero Member
*****

Karma: +79/-39
Offline Offline

Posts: 1421



« Reply #6 on: June 15, 2020, 06:14:26 AM »

Oh great I figure out your idea, it is excellent. Thank you
Only I have one problem, I can't make CLOSEST function
Even If I copy it from torquepro Wiki, i get error
https://torque-bhp.com/wiki/Equations#LOOKUP.28.7BVALUE.7D:.7BDEFAULT.7D:.7BKEY1.7D.7BOPERATOR.7D.7BVALUE1.7D:.7BKEY2.7D.7BOPERATOR.7D.7BVALUE2.7D:.E2.80.A6etc.29

EDIT: problem was in app, I instaled little earlyer version of torquepro. Now formulas working.
I made a even simpliest soultion, will post here after testing
One more thank you very much
« Last Edit: June 15, 2020, 12:09:01 PM by BlackT » Logged
Lechuga
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 41


« Reply #7 on: June 15, 2020, 06:34:25 PM »

Oh great I figure out your idea, it is excellent. Thank you
Only I have one problem, I can't make CLOSEST function
Even If I copy it from torquepro Wiki, i get error
https://torque-bhp.com/wiki/Equations#LOOKUP.28.7BVALUE.7D:.7BDEFAULT.7D:.7BKEY1.7D.7BOPERATOR.7D.7BVALUE1.7D:.7BKEY2.7D.7BOPERATOR.7D.7BVALUE2.7D:.E2.80.A6etc.29

EDIT: problem was in app, I instaled little earlyer version of torquepro. Now formulas working.
I made a even simpliest soultion, will post here after testing
One more thank you very much
Great. Looking forward to seeing your method

Sent from my ANE-LX1 using Tapatalk

Logged
BlackT
Hero Member
*****

Karma: +79/-39
Offline Offline

Posts: 1421



« Reply #8 on: June 17, 2020, 03:35:10 PM »

Working like charm
All you need is this

LOOKUP((val{Engine RPM}/val{Speed (OBD)}) ::80~1000=1:56~80=2:45~56=3:35~45=4:28~34=5:0~29=6)

When you press test in PID editor you can read the output when you shift gear. So it is really easy and fast to adapt it to any gearbox without any math

(Need to adjust first and second gear)
https://youtu.be/xG5EZvsMCXY

Logged
Lechuga
Jr. Member
**

Karma: +4/-0
Offline Offline

Posts: 41


« Reply #9 on: June 17, 2020, 09:36:42 PM »

That's brilliant!

I made some optimisations for the 6sp gearbox in the mk1 TT:

LOOKUP((val{Engine RPM}/val{Speed (OBD)}) ::110~150=1:69~80=2:45~56=3:34~44=4:28~33=5:0~28=6)

Sent from my ANE-LX1 using Tapatalk

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.018 seconds with 17 queries. (Pretty URLs adds 0s, 0q)