It is a little difficult for me since the CRD is not available in the US so cannot checkout. For Torque I would suggest installing the TorqueScan plugin also from the store and see what it finds.
Part of the problem is that OBD-II is a US standard. There are others such as the European OBD (EOBD) and EOBD2 which are similar but not quite the same.
Our current OBD-II uses the CANBUS protocol which is like any other LAN protocol. It needs to know both what device it is calling and with what command. It also need to know what response to expect.
Most inexpensive devices are only programmed to access the ECU and request/receive about 100 standard parameters. To access the transmission parameters you need to be able to select a different device and to make requests of it. OBDWiz/TouchScan have this built in, I am not sure about Torque but it does have the capacity to load custom commands and interpret the responses.
Part of the issue is that unlike GM, Ford, Toyota, Mazda, and BMW CJF is very secretive about the extended PIDs for things like Oil Pressure and Oil Temperature. They exist, we just have to figure them out by trial and error. This takes time and I do not have a lot to spare. I can interrogate the ECU and get a response, the issue is finding the specific PID.
Some third party providers have entered into PIAs with CJF to have access to such but are legally prevented from disclosing or even talking about them. If they do, CJF will cut them off. This leaves reverse engineering which is quite time consuming and may be destructive.
That said, vehicle speed is a required parameter (mode 1 PID 0Dh ), I do not know why you are having trouble. See OBD-II PIDs - Wikipedia, the free encyclopedia