nAst1: Progress and Concepts Thread

[robertisaar]

My thinking wasn't to make a module, just pipe the ABS sensor signals into the ECM and let the ECM retard spark as it needed for the requested/desired wheel slip.

AFAIK, there are only 2 free frequency based timers inside the 7727/similar that aren't used already, 1 is for VATS/MAF(depending on the mask that was being used). the other was only used on the Q4 for the 1X signal it's ICM creates to let the ECM to know which injector pair to fire.

now, since there are only 2 open, that automatically rules out running wheel speed sensors in there. i also have plans for those two inputs as well..... high frequency(~900-12,000Hz) MAF and as a 1X cam sensor for the VVT 3500/3900 motors for closed loop cam phasing control.



Ben, did TP actually show values while logging or just the blue bar showing a connection?

[pocket-rocket]

My thinking wasn't to make a module, just pipe the ABS sensor signals into the ECM and let the ECM retard spark as it needed for the requested/desired wheel slip.

[SappySE107]

Ok, figured out how to setup the ALDL and it says it was datalogging, but it won't let me save. It fails and then the backup to the install folder fails as well, and all is lost. That sucks.

[robertisaar]

^ that is EXACTLY how the 93-95 NorthStar PCM/ABS modules work. it watches the rear two wheels for a reference speed, and if the front tires start exceeding the speed of the rears, the ABS module will send a PWM signal to the PCM as a indicator of "requested" torque.

however, there are not enough inputs on any 7727 derivative to allow the same type of system. however..... if you knew how, you could build your own digital to analog converter and make a 0-5V signal for "requested torque", feed that into one of the many free A/D converters in a 7727 style ECM and then modify spark based off of that signal...

not difficult to impliment it software-wise on the ECM itself, but i have no idea how to make the DIY traction control module.

[pocket-rocket]

I wonder how an ECM (and ABS module for that matter) would react to piping 4 wheel sensors into it and using two for the reference wheels and 2 as the traction control attack modifier to reduce spark advance. Reason being, years ago when I was looking at aftermarket traction control systems, I didn't find any under $1k. Here is the one I wanted to get years ago that had full throttle shifting and launch control. With those options using stock ABS sensors the system came up to about $1500. Now it's £795, or $1,282.41 USD.

http://www.racelogic.co.uk/index.php/en/other-products/traction-control

I've had freescan work, but it always liked to disconnect at odd times. TP worked fine, and even went as far as to resume logging after the car was shut off for a bit and turned back on (found out on accident, lol, forgot to stop the log when I parked).

[robertisaar]

oddly enough, i've never been able to get freescan to work.

where are you getting hung up?

[SappySE107]

Or not I can never get tunerpro to datalog. I always use freescan on the GM OBD1.

[SappySE107]

Thanks I will just start from scratch on this and see how it ends up.

[robertisaar]

fixed the odd sections, imported teh nAst1ness.

EDIT: that one looks proper, but the one i just uploaded would be identical to one based off of the good one with the exception of the PROM ID.

[SappySE107]

BFAD Stock Read.bin

Nope, here is a copy of the stock chip. I don't even know why I kept that other version on my computer. Had to verify and this is the copy mine is based on.

[robertisaar]

And versatility All of this stuff should certainly make this an attractive mask to use by all sorts of people. I mean, if it's going to be a project for something other than stock cars, it may as well get features that non-stock cars would like to have I guess I didn't know (by definition) that a 2 step and WOT shift limiters were not the same.

AFAIK, 2 step means 2 rev limiters instead of one: one for on the line, another for while you're not on the line. that was what i had planned, but now it's transforming into a 3 step(on line, not on line, no lift shift)IMO.

[ATTACH]5891[/ATTACH]

Can you port this over. It is in my 94 cavalier wagon and now that I can put the wideband in, I will be able to test this code out on a stock 3.1 3 spd with 2.53 FDR. This is the stock file.

how sure are you that this BIN is good? i'm noticing some odd patterns around every $400 bytes... it's as if address pin 9 is acting odd during a read.

[SappySE107]

BFAD0127.bin

Can you port this over. It is in my 94 cavalier wagon and now that I can put the wideband in, I will be able to test this code out on a stock 3.1 3 spd with 2.53 FDR. This is the stock file.

[pocket-rocket]

getting all kinds of track goodies added lately.

And versatility All of this stuff should certainly make this an attractive mask to use by all sorts of people. I mean, if it's going to be a project for something other than stock cars, it may as well get features that non-stock cars would like to have I guess I didn't know (by definition) that a 2 step and WOT shift limiters were not the same.

[robertisaar]

hmm..... so while WOT(or near it at least), whenever you have the clutch pushed in(and for sake of the 2-step, above a certain MPH), you would want another rev limit?

i see what you mean now.... definitely something i'll have to integrate at the same time as the 2-step.

getting all kinds of track goodies added lately.

[pocket-rocket]

"no lift shift" ?

i would think you could use the normal rev limiter for that since it would still be in effect whenever the 2-step limiter isn't being used.

Well, yes and no. If I'm burning down the strip using a "no lift shift" I don't exactly like the thought of my engine free reving to 7,200 rpms while I shift. ~3500-4000 seems like a safer bet to me, and brings me right back into gear at the bottom of my power band, not to mention would be easier on synchros.