Quote from albuquerquefx on January 13, 2017
First time poster, very long time user.

I see you already support the SIGNED(value) function for 8-bit values, is there any possibility you might support a 32-bit signed value function as well?

Reason: There are two or three of us working on a Mode 23 raw memory block dump method for a very popular racing platform which, for now, shall go unnamed but is absent the wonderful Mode 23 capability. Turns out Torque Pro can be used to pull data in this way, but much of the data is 32-bit floats.

Given an OBD request of 23FFFF6DD80004 (using our proper header) I get a reply of 6341ABB732. The 63 is expected, this is a “good reply” acknowledgement. I want to drop the remaining data (in whatever way makes sense for your parser) into a SIGNED32(41ABB732) call and get back the float value of 21.4645.

The far larger use case for this is to pull back dozens of bytes at a time and use this single active PID as a reference value for dozens of virtual PIDs, which allows for _really_ fast logging out of a singular raw memory export (Mode 23) call.

I’m almost there! Can you help?

End Quote.

Please consider adding a function to convert
hex bytes to IEEE-754 32 bit floating point
values. This quote was posted in a pinned thread
by another user and may not have been noticed.

Float32(A,B,C,D)
Float32(E,F,G,H)

Hi!

That’s a relatively straightforward one to do, so I’ll get that into the current beta

EDIT: Completed – definitely in the next beta.