Hello

The example app just displays the ‘sensors’ that torque has seen-so-far since connecting, so it won’t initially be a full list.

If you want torque to go fetch something then you’ll have to ask it and give the ‘sensor’ it wants. basically most sensors are just the PID as parsed as hex and put into an int. So, Integer.toString(hex, 16) and Integer.parse(etc, 16) are your friends.

The next update of the api will enable some kind of exclusive mode (you can stop Torque from it’s casual ‘background’ scanning and ask it to do things specifically if you know what you want, so you have greater control (I need to do this for part of a simple scanner for extended PIDs I’m writing)

There may be bugs – if you have a whinge at my email (ian@prowl.org) I will have a go at fixing them!

If you have a specific requirement then I can see what I can do at getting something improved/added, though I can’t promise anything

Hope this helps!

Ian

Yes the next version of the TorqueScan plugin has scanning capability to at least find where the extended PID addresses are on different vehicles. Then after you know the address it’s a case of working out or searching for the information to go with them (Units, equations, etc).

Nice one Ian, many thanks!

May be getting in touch for some specifics…

Cheers!

i ran the scanner from the new addin to find pid adresses, what is that list telling me? command -> response

The scanner quickly scans the PIDs in the extended ECU segment (MODE 22, mostly) for more information. The command response is what is sent to the ECU and what is received (if a positive reply is given) NO DATA or negative replies are largely discarded unless they are a specific type of response. The utility is to be used for finding *part* of the PIDs supported. You will not have all the information (like formulas/equations, units and scaling, etc). You will still need to find that out for the PID you are interested in. You may be able to deduce some of it however.

ABS support is planned. I’m working towards this but it isn’t present (yet).

A reluctor ring? Maybe something that reads the individual wheel speeds would be useful. Should be easy to pinpoint troublesome rings then. I’m not sure how common ABS units are (I’m fully expecting them to be completley different an relatively non-standardised), but I’ll try my best to add features.

Hi

You’ll need to look for the extended PIDs for your vehicle manufacturer – then you will be able to add them to the app using the ‘Advanced Mode->Manage extended PIDs’ settings screens

TorqueScan isn’t really going to help you as it’s a development tool to allow people to find /where/ the PID blocks are, it won’t give you the important information like formulas needed to get the found PIDs to work.

You need to hunt around on the internet for the PIDs for your vehicle manufacturer. As cadillac is a division of GM, you may find that the GM predefined PIDs will work (that already exist in Torque, you just need to enable them using the menus described in my last post)

It will just appear on the main screen when you start the full version. You may need to go into the plugin settings and adjust the permissions for some of its scanning features. It will tell you if it needs that

Ian

I’ve had a good look around but not found anything yet on the net (though I think I found your post on another forum :))

The scanner will tell you where the PID ranges start (but will not scan each and every PID otherwise you’d be scanning for a week), it’s unfortunately impossible to know which is IAT2 without spending a *lot* of time looking at the output of the PIDs and how they change over time (ie: increasing as things get hotter). At the moment you would need to:

* Scan for the PID ranges.

* Use the telnet server to request the PIDs of interest over time manually and look at the returned values. (which is a bit complicated)