1994 GMC K1500 datastream Info Needed

Gizmo · Post by **Gizmo** » Fri Aug 06, 2010 8:21 pm

1994 GMC K1500 4x4 ext cab
350 tbi
Auto - 4L60E

16196395 < PCM
BJLH << Bin

I am trying to find the 'Slip' information in the datastream for the transmission. Viewing the datastream for message 0 works fine using the $0D mask files, but i do not see any slip information. I have started to log message 1 and have figured out a few things from it, but am not seeing a slip value thus far. I am assuming each message shows different diagnostic info, as in message0 seems to show engine data, thus was hoping to find transmission data on message 1. Is there a list of what is in each message? Does someone have a breakdown of the different messages for this particular setup.

Gizmo

Post by **robertisaar** » Sat Aug 07, 2010 7:09 am

moatesuser

moatespassword

if it asks...

http://www.moates.net/files/4)%20Datastream%20Definitions/ALDLstuff.zip

(you'll have to copy/paste the link, clicking alone will lead to a 404 error)

look at A218.DS, that will show you the tranny information you're looking for. bytes 46 and 47 of the first datastream.

this information should already be in an ADS or ADX though...

Gizmo · Post by **Gizmo** » Sat Aug 07, 2010 11:21 am

Message 0 data seems to line up with the A217 breakdown vers the A218 breakdown. I tryed to apply the A218 breakdown to message 1 data, and it doesnt line up with correct information.

Post by **robertisaar** » Sat Aug 07, 2010 11:26 am

doesn't line up?

odd...

ADS or ADX, and does it list the author?

and yes, 217 should line up perfectly with message0.

Gizmo · Post by **Gizmo** » Sat Aug 07, 2010 11:34 am

I built the ads using the data breakdown out of the A218.ds file. I am also looking at the raw data, as in doing a manual breakdown in notepad as I go. For example mode1 message1 Byte6 shows my battery volts, byte19 is coolant temp.

Gizmo · Post by **Gizmo** » Mon Aug 09, 2010 8:06 pm

Well A218 datastream lines upto the data correctly when one sends the correct command packet for the data that is wanted. I was sending $F4... instead of $F5... So rebuilt the .ads file useing the corrent command and gettting the data that I want. Thanks for the help

Gizmo · Post by **Gizmo** » Mon Aug 09, 2010 9:15 pm

Any ideas on how to get TunerProRT to display the slip correctly , as in it is a signed number, so how to show that in the display correctly.

Post by **robertisaar** » Mon Aug 09, 2010 9:18 pm

IIRC, the 2's compliment option will fix that... i think.

Gizmo · Post by **Gizmo** » Mon Aug 09, 2010 10:23 pm

I dont see where that is.

Post by **robertisaar** » Mon Aug 09, 2010 10:39 pm

whoops, must have been thinking of something else. click on the general tab of the value, under "units override", on the right side, there is a checkbox for a signed value.

Gizmo · Post by **Gizmo** » Thu Aug 12, 2010 4:29 pm

Sorry I still dont see where. I see where in a xdf, but not an ads

Post by **robertisaar** » Thu Aug 12, 2010 4:39 pm

and now i know why.... i was thinking of TPV5, not V4...

and honestly, i have no idea how signed values work. does it take all of the bits except for the least significant or most significant bit and use those for magnitude, and the final bit is for direction?

or am i way off?

Gizmo · Post by **Gizmo** » Thu Aug 12, 2010 7:25 pm

Signed numbers use the highest bit to hold the sign.
0x7F = 01111111 = 127d so our range with 8 bits is -127<>127d
If high bit is set = negative value.

Post by **robertisaar** » Thu Aug 12, 2010 7:33 pm

ok, that's about what i expected... so is it a dual-byte value as implyed by the DS?if it's a single byte, that's VERY easy to setup, just make a lookup table and just throw in 4 values, the highest positive, lowest positive, lowest negative, highest negative...

i did the very same thing for an ABS definition i made the other day. since TP intterpolates the values, you only need to enter those four. possibly the 0 value, but still.

a 16-bit would work the same, just on a much larger scale.

Gizmo · Post by **Gizmo** » Thu Aug 12, 2010 7:59 pm

Unfortunatly yes its a 16 bit value for this instance

Post by **robertisaar** » Thu Aug 12, 2010 8:04 pm

not necessarily harder, just have to make a 65536 entry lookup table(assuming V4 won't crash because of it).

Gizmo · Post by **Gizmo** » Thu Aug 12, 2010 8:13 pm

32,000 is the high limit on tables

Post by **robertisaar** » Thu Aug 12, 2010 8:17 pm

you may need to jump up to V5 then...

Gizmo · Post by **Gizmo** » Thu Aug 12, 2010 8:19 pm

I didnt see a version 5 for downloads

Post by **robertisaar** » Thu Aug 12, 2010 8:25 pm

http://tunerpro.net/

scroll down a bit, and you'll see this link.

http://tunerpro.net/beta/tpbeta.htm

Gizmo · Post by **Gizmo** » Thu Aug 12, 2010 10:49 pm

Thanks, I'll have to give that a try as ive noticed some other errors ive had with v4. I hope all this work building an ads file for a218 imports to v5. Or is there one for v5 around? I'll have to test out v5 on my laptop first before making the jump, as its win2k p366, anything I have bigger doesnt have a serial port on it.

Post by **robertisaar** » Fri Aug 13, 2010 7:05 am

you can import the ADS into V5, but you'll have to set all of the values and bits to the correct command response since that doesn't seem to transfer over...

also: the cheapest serial-usb adapter that works: parallax 28031, it's what i use for mine, i couldn't stand ancient laptops just because they had serial ports...

Gizmo · Post by **Gizmo** » Fri Aug 13, 2010 8:25 am

I tryed my prolific usb->rs232, and was a no go:( I'll have to grab a diff manufacturer and try it, was thinking the ftdi ones, or just order up some samples from ftdi

Post by **robertisaar** » Fri Aug 13, 2010 8:29 am

FTDI are the ONLY ones that seem to work reliably...

the parallax model uses the FTDI FT232RL(IIRC)