3 byte values in ads streams?

LittleNo · Post by **LittleNo** » Fri Jun 24, 2005 9:21 am

hey folks!

i just tried to write a ads file for the 95 Northstar Eldorado, and found there a little problem: in the stream of that car are 3 byte long values used. as far as i know, i can only handle 2 byte (16 bit) values in TunerPro, right?

and btw: have you thought about a better feature for "calculating" values? i mean, at the moment i can multiply and divide values, but what is with complexer calculations? i wrote some ads files for newer cars the last weeks, and had this problem some times, where i had to calculate more than this simple things...

Post by **Mangus** » Fri Jun 24, 2005 11:11 pm

Hi. What DS file does the Northstar use? I haven't run into 3 byte stream values yet. In any case, I can implement support for it.

Regarding complex calculations, I plan on re-writing the ADS format (again) to resemble the XDF format, so calculations should be as complex as you'd like.

LittleNo · Post by **LittleNo** » Sat Jun 25, 2005 12:13 am

its the A254.DS

you find this in the 88 byte stream in bytes 63 to 65

this is not such a important value, but it would also be nice to be able to handle this