The custom PID edit window mentions A<8 in its example string, and after testing it I confirm that Torque supports shift operators x<n and x>n in equations.

Hi,

Does Custom PID's support "if" and "else" statements like in asp/php/vb ?

if ([0xff1208] < 7.0) A="ON" else A="OFF"

I'm trying to build a Custom PID which will display a static text as output value.

Any help will be great ...

These are all the ones that Ian has ever announced. Might search the change-logs for more, but this is the most comprehensive list of operators that I could come up with after nearly a week of searching through forum topics.

Hi,

I'll monitor the changelogs for future implemantations but for now as far as searched and understood "if" statements are not possible 🙂

I'll try my chance for a simple "0" / "1" result with below equation ;

[0xff1208] < 7.0

So if above code returns 1 then at least I can use the simple on/off display and this will be a good start.

I tested this custom pid without connecting to ecu, the result was 0 and it did not gave an error.

I will post my test results earliest tomorrow at my Fuel Economy Display topic.

Thanks for the reply and detailed list post.

Best wishes

For the ON/OFF display to work, all you need is to be above 0 for ON and 0 or less for OFF.

The "

Is there someone that could explain what do to a value?

I mean what is the effect to put A < 16 or B < 8 to an equation?

What is the difference to use X < 16 or X < 8 ?

Normally are smaller than and bigger than

they are normally use with the if command they don't change the value it's a check

if value A is > than 16 response is 1 (or on) other wise response is 0 (off)

http://en.wikipedia.org/wiki/Logical_shift

moreause, you are wrong - Torque use those as shift operators, not compare operators

so if i put in the equation "A < 16" the binary value of "A" is shifted to left by 16 bits,

if

"A < 8" the binary value of "A" is shifted to left by 8 bits
"A < 4" the binary value of "A" is shifted to left by 4 bits

and so on...

it's correct?

a that make more sens

but if i understand correctly since A is a 8 bit value
shifting it by 16 would be equal to set it to 0
unless the end bit become the first bit...

Quote from Hiej on November 5, 2014
...
it's correct?

yes, that is correct. Though that time moreause is also correct - that makes no sense to shift to more than 7 bits to the right, as all variables A,B,C,D,E,F are byte values (thus having only 8 bits), so shifting to 8 or more bits to the right is equal to setting those to 0. When shifting to the left, byte values will be expanded to words or dwords, as internal calculations are made in 32 bit.

Quote from frodus on March 7, 2014

{A:b} — returns the bth bit of the byte A. Least significant bit is 0, example A = 00001010b = 09h, {A:0} = 0; {A:1} = 1

error example A = 00001010b = 09h
must be A = 00001010b = 0Ah

If bit logic is reversed...

ABS({A:b}-1)

Expect parser is not accepting as written.

or

1-{A:b}

Suggested by Cintakc.

Edited.

Thanks Capp777

Good for us old members with poor memory also.

Quote from admin on April 21, 2016
Hi! Right! - in the 1.8.92 update you're going to get a new set of variables that you can use in the equation parser...

Torque traditionally takes some of the hard work away when dealing with responses (which is why you don't immediately need to start of with variable D in a lot of cases). The variables starts from A, B, C, for mode 21, 22, 01, etc where the data headers and response status have already been removed for you. (these are also mirrored by variables N0, N1, N2 (etc) for simplicity)

However, with some awkward manufacturers, they may reply with no header at all (with useful information at the start of the packet that you'll want to get at).

To get the variables for the *whole* raw data reply, you can now use the following variables:

R0, R1, R2, R3 (etc) where in most cases R3/4 would equate to 'A' in normal mode21/22/01 messages (depending if you're using canbus or an iso protocol like 9141)

So, R0 ('Raw 0') will get you the absolute start of the message, which should give you access to the bytes you want

So the equation would now look like:

R0 * 5

For the first value in the reply

End Quote.

What about the length (number of bytes) of the received data? Is it available in a variable to be used in a formula?

1. VAL{sensor name}
Where can I see a full list of sensor name?

2. can I know the name of the variable "tank capacity" from the profile

Quote from DANGER1979 on April 28, 2016
1. VAL{sensor name}
Where can I see a full list of sensor name?

2. can I know the name of the variable "tank capacity" from the profile

End Quote.

The easiest way is to use Torquescan which
will display the long names of all the pids
known to Torque.

The variable “tank Volume” - in TorqueScan not available.
I want to use this variable in the formula customs PIDs.