Page 4 of 5

Re: 1990 Geo Storm GSi Turbo

Posted: Mon Jul 15, 2013 11:51 am
by VL400
90base wrote:Here is the first code I entered and the response that I got.
16:25:39.716 Tx'd Frame = F4, 56, 1, B5,
16:25:39.803 Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, AB, 6C, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 5, 0, 80, 50, 48, 74, 76, 0, 7B, 2, 3C, 80, 20, 0, 0, 56, 12, 26, 23, 37, 0, 0, 0, 0, 0, 48, 0, 0, 0, 4C, 0, 0, 1B, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 0, 1F, 40, CC,
Its a big frame but it does reply. What you can try is sending the request a few times with the engine off, starting it and sending it some more. If its a correct response RPM should be in there so you will see a byte change. There are bytes changing in there.

90base wrote:Here is the second ommand that I entered and the response that I got.
16:26:27.293 Tx'd Frame = F4, 58, 2, 0, 0, B2,
16:26:27.384 Rx'd Frame = F4, 95, 2, FF, FF, FF, FF, 7F, 0, 0, 0, 0, 0, 0, 12, 26, 20, 15, 0, 1, 0, 0, 0, 70, 70, 50, 0, F0, 74, 23, 1B, 13, 0, A, 0, 0, 1, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 40, 20, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 15, BC, 0, 0, 21,
Well its good you got something back, but the problem is the ECU is short changing you! Normally a mode 2 command returns 64 bytes of data from a particular address (the 0,0 in the command says from address 0x000), your only getting 63 bytes (which is what the flashtool reported when you tried to connect the other day).

Now the coincidence here is both requests returned the same frame length. The first request is for engine data, a 63 bytes payload for that is very large in the Aussie ECU world. I think the easiest thing is to read the memcal and then go through it that way. Could waste ages trying to get logging working but you still cant read the bin to even think about making any changes.

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 16, 2013 2:04 am
by 90base
So why would the ecu only send back 63 bytes of data when we are expecting 64? Is it because it's not reading from the right place?

Thanks

Brandon

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 16, 2013 6:19 am
by 90base
Okay I solder up a more permanent cable and send the following command 5 times with the engine off and 5 times with it running the the results are as flollows::

Code Sent

Code: Select all

F4,56,1,B5

RECEIVED:
KEY ON ENGINE OFF

Code: Select all

16:14:56.029     Tx'd Frame = F4, 56, 1, B5, 
16:14:56.116     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 2, 0, 80, 50, 5B, 74, 76, 0, 78, 6, 5C, 80, 20, 0, 0, 22, 1E, 26, 23, 39, 0, 0, 0, 0, 0, 48, 0, 0, 0, A3, 0, 0, 18, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 17, 1F, 40, B7, 
16:14:57.602     Tx'd Frame = F4, 56, 1, B5, 
16:14:57.691     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 2, 0, 80, 50, 5B, 74, 76, 0, 78, 6, 5C, 80, 20, 0, 0, 22, 1E, 26, 23, 39, 0, 0, 0, 0, 0, 48, 0, 0, 0, A3, 0, 0, 18, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 17, 1F, 40, B7, 
16:14:59.712     Tx'd Frame = F4, 56, 1, B5, 
16:14:59.801     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 2, 0, 80, 50, 5B, 74, 76, 0, 78, 6, 5C, 80, 20, 0, 0, 22, 1E, 26, 23, 39, 0, 0, 0, 0, 0, 48, 0, 0, 0, A3, 0, 0, 18, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 17, 1F, 40, B7, 
16:15:00.527     Tx'd Frame = F4, 56, 1, B5, 
16:15:00.616     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 2, 0, 80, 50, 5B, 74, 76, 0, 78, 6, 5C, 80, 20, 0, 0, 22, 1E, 26, 23, 39, 0, 0, 0, 0, 0, 48, 0, 0, 0, A3, 0, 0, 1A, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 17, 1F, 40, B5, 
16:15:01.440     Tx'd Frame = F4, 56, 1, B5, 
16:15:01.530     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 2, 0, 80, 50, 5B, 74, 76, 0, 78, 6, 5C, 80, 20, 0, 0, 22, 1E, 26, 23, 39, 0, 0, 0, 0, 0, 48, 0, 0, 0, A3, 0, 0, 1A, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 17, 1F, 40, B5, 
[b][u][i]WITH ENGINE RUNNING
[/i][/u][/b]16:15:35.420     Tx'd Frame = F4, 56, 1, B5, 
16:15:35.510     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1A, 0, 2A, 0, 7, 4C, 0, 2C, 0, AA, 5E, 70, 39, 5B, 74, 37, 0, 8A, 1, 3F, 5C, B0, 0, C, 88, 1F, 26, 23, 30, 0, 0, C8, 0, 0, 24, 0, 0, 0, A3, 46, 0, 1C, 2, 80, 0, 0, 60, 0, 2, 1, 8, 89, 17, 1A, 64, 32, 
16:15:38.942     Tx'd Frame = F4, 56, 1, B5, 
16:15:39.030     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1A, 0, 29, 0, 7, 73, 0, 2A, 0, BE, 57, 70, 39, 5B, 74, 35, 0, 8B, 1, 29, 55, B0, 0, 10, 88, 1F, 26, 23, 30, 0, 0, C8, 0, 0, 24, 0, 0, 0, A3, 46, 0, 1E, 2, 80, 0, 0, 40, 0, 2, 1, 0, 89, 17, 1A, 64, 41, 
16:15:40.202     Tx'd Frame = F4, 56, 1, B5, 
16:15:40.291     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 62, 54, FF, 1A, 0, 2A, 0, 7, 4D, 0, 2D, 0, 21, 5E, 70, 39, 5B, 74, 38, 0, 8B, 1, 4C, 60, B0, 0, 11, 87, 1F, 26, 23, 30, 0, 0, 88, 0, 0, 24, 0, 0, 0, A3, 46, 0, 1E, 2, 80, 0, 0, 60, 0, 2, 1, 0, 89, 17, 1A, 64, E8, 
16:15:42.129     Tx'd Frame = F4, 56, 1, B5, 
16:15:42.219     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 63, 53, FF, 1A, 0, 2A, 0, 7, 65, 0, 2B, 0, 1D, 5B, 70, 39, 5B, 74, 36, 0, 8B, 1, 36, 5D, B0, 0, 13, 89, 1F, 26, 23, 30, 0, 0, 88, 0, 0, 24, 0, 0, 0, A3, 46, 0, 1C, 2, 80, 0, 0, 60, 0, 2, 1, 0, 89, 17, 1A, 64, F2, 
16:15:42.795     Tx'd Frame = F4, 56, 1, B5, 
16:15:42.884     Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, 63, 53, FF, 1A, 0, 2C, 0, 7, B, 0, 2B, 0, 41, 61, 70, 39, 5B, 74, 36, 0, 8B, 1, 41, 63, B0, 0, 13, 89, 1F, 26, 23, 30, 0, 0, 88, 0, 0, 24, 0, 0, 0, A3, 46, 0, 1C, 2, 80, 0, 0, 40, 0, 2, 1, 8, 89, 17, 1A, 64, 27, 
I see alot of variables changing.

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 16, 2013 3:08 pm
by VL400
Attached is an ADX with the 30 bytes so you can watch things changing with the engine on and off. You really need to get a bin to go much further with it, but you might be able to ID basic things like RPM (possibly byte 10), coolant and intake temp.

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 16, 2013 3:37 pm
by 90base
WOW THANKS!!

I really appreciate your help! Ill try this tomorrow and see where I can get. Ill work on getting the bin as well. I may have to buy a chip burner as suggested above.

Thanks

Brandon

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 16, 2013 5:12 pm
by charlay86
A chip burner will be very handy if you want to be able to tune this thing in the future.

you can easily figure out which one is tps by putting your foot on the throttle.

as noted by VL400 byte 10 could be be rpm, multiply the received value by 25 to get the actual value
rpm/desired idle rpm? 0x2A = 42d => 42 * 25 = 1050 rpm (byte 15 could be desired idle speed)

bytes 12-13 are possibly the reference period (time between successive reference pulses):
0x0773 = 1907d
(1/1907)*65536 = 34.36 bangs/second
34.36*(60 seconds / 2 bangs per rotation) = 1031 rpm

Re: 1990 Geo Storm GSi Turbo

Posted: Sat Jul 20, 2013 4:40 am
by 90base
I tried the adx file and all I ever get is connecting.

So why would the ecm be "shortchanging" me?

I know a local guy with a burn 2.im trying to get it off of him.

Thanks

Brandon

Re: 1990 Geo Storm GSi Turbo

Posted: Sun Jul 21, 2013 9:50 am
by VL400
Give this one a try, missed a couple of things.
90base.adx
(13.15 KiB) Downloaded 515 times

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 23, 2013 7:50 am
by 90base
Alright,

VL400, Thanks for the ADX FILE I really appreciate all the help that you have given me. I am still looking locally for a Burn2 but If I have to buy one online thats what I will do.

I tried the second ADX file and it flashes between connected ad error constantly although does have a Latency time that keeps changing between like 1.6 and 3 hz.

What could that be? I wish I had alot more time and money to devote to this but I will get there eventually right now, the main concern is some tires, balljoints, and tierod ends.


Thanks

Brandon

Re: 1990 Geo Storm GSi Turbo

Posted: Tue Jul 23, 2013 9:45 am
by VL400
Try this one, added a delay between requests.
90base.adx
(13.36 KiB) Downloaded 583 times
If it still does not work you might have to play around with the settings yourself, its hard to test without the ECU. And even when it does work you will still have to spend a heap of time figuring out the bytes.