Hi,

I’m currently on Torque Pro version 1.8.49 and I upgraded to the latest version 1.8.80.

This upgrade broke all my Extended PIDs which were all working fine with 1.8.49.

Below you will find the Extended PIDs I’m using. I have effectively prefixed all the addresses with “a0”. For example, the address for my AFR PID in EvoScan (a logging app for PCs) is 38. To get this to work in Torque I change the address to be A038. I remember reading this on another website but for the life of me I can’t find it.

Anyway, here’s the file I imported into Torque 1.8.49 and it worked just fine. Please help?

Name,ShortName,ModeAndPID,Equation,Min Value,Max Value,Units,Header
[Evo]Load1Byte,Load1Byte,a041,A*1.2,0,350,load,
[Evo]Knock Sum,KnockSum,a026,A*1.2,0,10,count,
[Evo]MIVEC,MIVEC,a042,72-0.6*A/32,0,30,degrees,
[Evo]AFRMap,AFRMap,a032,(14.7*128)/A,7.4,19.4,afr,
[Evo]AFR,AFR,a038,(A*0.0392156862745098)+9.6,9.6,19.6,afr,
[Evo]OctaneLevel,Octane,a027,100*A/255,0,100,%,
[Evo]AirflowHz,Airflow,a01a,6.25*A,0,1650,hz,
[Evo]InjPulseWidth,InjPulse,a029,0.256*A,0,66,ms,
[Evo]InjDutyCycle,InjDuty,a021,[a029]*31.25*[a021]/1200,0,160,%,
[Evo]FTLow(LTFT),FTLow(LTFT),a00c,(0.1953125*A)-25,-25,25,%,
[Evo]FTMid(LTFT),FTMid(LTFT),a00d,(0.1953125*A)-25,-25,25,%,
[Evo]FTHigh(LTFT),FTHigh(LTFT),a00e,(0.1953125*A)-25,-25,25,%,
[Evo]FTInUse(LTFT),FTInUse(LTFT),a050,(0.1953125*A)-25,-25,25,%,
[Evo]O2FT(STFT),O2FT(STFT),a00f,(0.1953125*A)-25,-25,25,%,

Shouldn’t the fields in your file be enclosed
in quotes? Look at Other.csv as a template.

Hi!

Since MUT support was added, I can’t remember getting feedback about it so it may not be working (I never had feedback to say if it did work or not iirc)….

In an effort to see what’s up and get it working, can you send me a debug log and I’ll take a look

To do this, go into the ‘General’ settings and scroll to the bottom and tick ‘Enable Debugging’ then quit and restart the app

After this let it connect to the adapter and go to the ‘Realtime Information’ screen (with one of the affected sensors added as a display). Let this run for 30 seconds, then press menu-}send debugging info

In the box that pops up, type your forum name and ‘MUT’ in there then press ‘Send’. If it sends ok you should see a ‘sent ok’ message at the bottom of the screen.

I’ll then have a look at the debug and will try to get things back up and running for you

Sent the debug sucesfully, hope you get it ok

Awesome, thank you!

Hi!

Ok! managed to sort the kiwi3 out (waiting on PLX now) so I can now look at MUT support tomorrow morning. Got to update my test harness for it then should be able to get to the bottom of what’s up with it. Apologies for the delay!

Hi,

We are waiting for a solution since version .49. Do you have any idea why the MUT custom pids don’t work anymore?

Thanks.

Hi, I’m also having some problems with extended PID’s. Im not sure if it’s related to this update since I have just started using extended PID’s.

I have a somewhat similar but unique situation since my car is a 1992 Mitsubishi 3000GT. It’s OBD1. I built an adapter that converts the 1953 buad rate of the ECU to 9600 baud for regular serial communication.

Basic setup is:
ECU—RS232—AVR Mico—Bluetooth—Torque.
The RS232 adapter converts the 0-12V half duplex signal to 0-5V TTL. The micro coverts 1953 baud to 9600. It also decodes commands from Torque to commands that the ECU understands.

The setup works fine when I run the custom PID “Test” in torque. I can add about 3 sensors to one dashboard and it will work fine. If I add one more things go crazy. Some displays stop updating and others start showing wrong data.

More details:
The ECU is a single byte request – single byte reply system.
Example for “Throttle Position”:
My ECU expects “0x17” (or 23 in dec). It will reply with 0x00 to 0xFF.
OBD Mode and PID: 0F17.
Long name: Throttle Position.
Short name: T.P.S.
Min:0
Max:100
scale:1x
Unit: %
Equation: B*100/255
OBD header: (Blank, empty line)
Diag start: (Blank, empty line)
Diag stop: (Blank, empty line).

When I run the test I see a response from 4F00 to 4FFF based on how far I press the accelerator.
The equation correctly outputs 0-100%.

Not sure if this will hijack the thread, let me know if I should start my own.

Update today should fix the issue with MUT!