problems with twecer

[somedude_001]

all of the sudden i'm having problems with my tweecer. I was fooling around with it this weekend basicly just browsing through the software to make sure everything was working correctly (see notes below) and to correct the idle i was toying with last time i broke out the laptop. I had the idle set at 350rpm so it was a super sneaky roll up for meets and stuff on settings 1 and 3 and all stock settings except for the file i got from axanator (sp) a while back on settings 1,2,3,4. well I re wrote all the banks to the file i got from axanator and on position 4 and 2 (which have always mirrored each other) it fails to write "null write" and locks up caledit every time. here is the symptoms,

position 0 (off) = everythin works normaly
position 1 = shifts better than stock with redline of 7500 (more comments below)
position 2 = engine off: check engine light flickers really fast fuel pump stays on and injecters fire (with engine off) this has to be a major fire hazzard
position 2 = engine running: all the lights on the dash go crazy engine will die unless the rpms are way up before you switch to this position then i believe it is holding most of the injecter open al the time as noted by the dangerously strong gas fumes.
position 3 = car lacking power and pops and backfires above 6500 (i've tried re writing the same program that i stated above but does not help)
position 4 = same as position 2

i keeps failing to write to bank 2 and 4 it just says "null write" and locks up, when i first click write the car settles down turns the cooling fans and pump off and stops the mass relay clicking from under the hood untill it locks up then it goes crazy again.

the only thing i didn't try was unpluging the unit and writing to is out of the car. I did try reseating it in the car with no change though but did not write to it after reseating it. (yes its taped it tight)

note 1 : I wanted to make sure everything was working correctly on my twecer because i had to read the EEC on my friends turbo probe so we could send the information to twecer. he is in need of a tunning program and doesnt want to use megasquirt, twecer said they don't support the probe but have not looked at the computer either. they asked if i could read his eec with my twecer or have him send in his spare computer to take a look at it.

note 2 : with the redline increased my first gear goes to about 50mph and second gear is 94mph, it is pretty cool to hear that thing screaming like that . yes its a ATX

any thoughts? i need to send this in for the data logging one but i need moe info on this first.

 

[Speedy_91_SHO]

Make sure your bank count is set at 1. I was having the same problem and that was the culprit.

 

[Axianator]

all of the sudden i'm having problems with my tweecer. I was fooling around with it this weekend basicly just browsing through the software to make sure everything was working correctly (see notes below) and to correct the idle i was toying with last time i broke out the laptop. I had the idle set at 350rpm so it was a super sneaky roll up for meets and stuff on settings 1 and 3 and all stock settings except for the file i got from axanator (sp) a while back on settings 1,2,3,4. well I re wrote all the banks to the file i got from axanator and on position 4 and 2 (which have always mirrored each other) it fails to write "null write" and locks up caledit every time. here is the symptoms,

Rather than using your existing (modified) calibration files, have you tried writing a purely-stock factory D4U1 image into any of the four program positions? As Speedy_SHO has noted, a misconfigured bank count can cause symptoms similar to what you've described. Make sure that you're TwEECer is configued to accept four 2-bank programs and that your bank count is set to '1' before uploading any programs (see the TwEECer Getting Started manual for more information on how to do this).

I had the idle set at 350rpm

350 RPMs - is that a typo?

when i first click write the car settles down turns the cooling fans and pump off and stops the mass relay clicking from under the hood untill it locks up then it goes crazy again.

This temporary "settling down" is due to the TwEECer switching itself off while it receives the file from your laptop, which effectively returns control of the show back to the EEC and allows it to use the factory image while the TwEECer is reading it's data.

the only thing i didn't try was unpluging the unit and writing to is out of the car. I did try reseating it in the car with no change though but did not write to it after reseating it. (yes its taped it tight)

Did you reseat and/or remove the TwEECer module from the computer while in KOEO? If so, then you may have damaged your module.

note 1 : I wanted to make sure everything was working correctly on my twecer because i had to read the EEC on my friends turbo probe so we could send the information to twecer. he is in need of a tunning program and doesnt want to use megasquirt, twecer said they don't support the probe but have not looked at the computer either. they asked if i could read his eec with my twecer or have him send in his spare computer to take a look at it.

Let me know if you and/or your friend are not able to get anywhere with Mike re: a .dat file for your friends Probe PCM and I will add his calibration file to my list of future software developement.

any thoughts? i need to send this in for the data logging one but i need moe info on this first.

Give the bank reconfiguration a try first, then report back the results. If your module continues to misbehave in the manner you've described, you may need to return/exchange it to Mike for a new unit.

 

[somedude_001]

a misconfigured bank count can cause symptoms similar to what you've described. Make sure that you're TwEECer is configued to accept four 2-bank programs and that your bank count is set to '1' before uploading any programs

i thought the bank count had to match the switch position. i'll try rewriting it with it on bank count one on those 2 slots.

i'll keep you posted on the probe data.

no that wasn't a typo it actually runs smooth as silk at 350rpms i tried 300 but the oil pressure light comes on and it stalls sometimes. its almost comical to have a massive exhaust leak with a 350 idle because it is totaly silent with the hood closed then a litle blip of the throttle and its loud as **** again.

 

[Axianator]

i thought the bank count had to match the switch position. i'll try rewriting it with it on bank count one on those 2 slots.

The bank count actually has to do with number of banks that CalEdit will attempt to write to the TwEECer module. Pre-'96 EEC-IV processors utilize 1-bank (64 KB) programs while '96+ EEC-V processors can utilize 2-bank (128 KB) or 4-bank (256 KB) programs.

no that wasn't a typo it actually runs smooth as silk at 350rpms i tried 300 but the oil pressure light comes on and it stalls sometimes. its almost comical to have a massive exhaust leak with a 350 idle because it is totaly silent with the hood closed then a litle blip of the throttle and its loud as **** again.

Do you have any video of this unique modification in action?

 

[somedude_001]

i'll see what i can do but no promises

 

[RJ-92]

no that wasn't a typo it actually runs smooth as silk at 350rpms i tried 300 but the oil pressure light comes on and it stalls sometimes. its almost comical to have a massive exhaust leak with a 350 idle because it is totaly silent with the hood closed then a litle blip of the throttle and its loud as **** again.

I wouldn't recomend that. You are farmiliar that the SHO oil pressure at normal (~800-900) idle is already quite low. My gauge reads ~12.5 at my idle and its raised 100 RPM over stock.

I'm guessing your OP @ 350 RPM is ~6psi, there's a reason your light comes on any lower. Your rod bearing are pist at you.