Besides using Val{} or [xx], is there a way for
the user to extract the extra bytes from another
pid? (One request to populate multiple user
pids with same pid number to increase pid
read speed).

Similar to what you (Ian) are doing with OBD
pids predefined in Torque.

I suppose that it isn’t job of ‘torque’. If your ECU is fully compliant with UDS standard (ISO 14229-1) then you may use service id (SID) DynamicallyDefineDataIdentifier=0x2C for crafting your own data identifiers which would then returns many PIDs by one request.
You may try to insert such definition in initialisation string.
It should significntly increase the speed of data reading

According to this standard, if you have two dataId ( for example 1800 and 1801) which you are reading by two different requests

22 18 00
22 18 01

then you may craft your own dynamic dataId (for example F3 01) by the next command

2C 01 F3 01 18 00 01 02 18 01 01 02

and after that you should be able to read both parametres at once with the next command

22 F3 01

In this example 01 02 after 18 00 means that ECU should get 2 bytes beginning from firs byte of first request and similar for the second request. The result would be sent to ELM in one responce

Yes – this example for mode 22 (in term of torque)

I suppose that the torque do not send two equal consequent requests for parsing two data fields which both are in every response. If I were the developer I would do so

Quote from Shr-lnm on August 30, 2017
then you may craft your own dynamic dataId (for example F3 01) by the next command
2C 01 F3 01 18 00 01 02 18 01 01 02

I think the adapter ELM327 can not issue requests longer than 8 bytes

Elm command ATAL.

Programmatically, of course you can implement long requestes, I read your review on the link,
but it’s impossible to make a user in a Torque.

Thanks, download, you can delete the link.
why I asked, because it’s complicated for BMW
example:
2C 03 F3 00
04 6C 03 F3 00
2C 01 F3 00 4A F1 01 02
04 6C 01 F3 00
22 F3 00
05 62 F3 00 50 A9

Quote from Shr-lnm on August 30, 2017
The problem is a bit more complex ). ATAL for CAN allows to send 8 bytes instead of 7, but you still couldn’t send 9 bytes for example.
Look in my blog above

End Quote.

My understanding of SAE J2190… it allows sending
multiple requests to build the packet contents using
less than 8 data bytes per request.

The ATAL would be for the oversized response when
requesting the packet.

My vehicles range from 1995 – 2004 model years
where what you are describing won’t apply.

Torque still won’t let me populate multiple custom
pids with a single response though?

Edit:

Ian has just posted on another thread that multiple
requests to the same pid in the same loop will be
answered by the cached response during that loop.
Eliminating the extra network traffic. Requires that
the pid be the same.

https://torque-bhp.com/forums/?wpforumaction=viewtopic&t=9152.0