tweecer problems

[sn-95matt5-0]

well i installed my tweecer about a month ago. and had problems with it. the tweecer would read the eec but it wouldn't be right. like for instance my idle rpm was set at 19000 which i really dont think it should be set at. but the whole time the car idle like normal and had no problems. since i had this problem i have removed the tweecer and cleaned the j-port and the port on the tweecer. still had the same problem.


has anyone had any problems with their tweecer?


done searches but it ended in a dead end

 

[Blackened302]

how did you go about cleaning the port?

reason i ask: it has a clear, gel-type coating that you need to scrape off w/ a razorblade or something (carefully, of course).

 

[sn-95matt5-0]

i used a small screw driver and then rapped the screw driver with a rag dipped in alcohol. i have seen threads where this is wat was done.

 

[reddy351]

Where'd you buy it? Maybe it needs to go back?

 

[BlownFiveLiter]

Moved to 94-95 Tuning.

 

[sn-95matt5-0]

i was afraid something was wrong with it and it needed to go back. but i was hoping i was just doin something wrong. its been awhile since i bought it so i doubt they will take it back.

 

[Stanger007]

The last time I tried to do a stock read, I also got the same problem. Tried it again yesterday and still getting odd #s. This is with CalEdit *OR* BinaryEditor.

It is not a huge deal for me, as I have the stock tunes already, but I can verify that it did work waaay back when I first got the twEECer.

You can find some stock tunes here: http://fordfuelinjection.com/bins/

Reading off positions 1-4 is a-ok, I have been doing this on a weekly basis through both BE and CalEdit. It's that position 5 that is hosed.

Perhaps something is wrong with the driver? Regardless, Mike Glover should be able to help you out.

Wes

 

[final5-0]

The last time I tried to do a stock read, I also got the same problem. Tried it again yesterday and still getting odd #s. This is with CalEdit *OR* BinaryEditor.

It is not a huge deal for me, as I have the stock tunes already, but I can verify that it did work waaay back when I first got the twEECer.

You can find some stock tunes here: http://fordfuelinjection.com/bins/

Reading off positions 1-4 is a-ok, I have been doing this on a weekly basis through both BE and CalEdit. It's that position 5 that is hosed.

Perhaps something is wrong with the driver? Regardless, Mike Glover should be able to help you out.

Wes

I've never tried it myself ... but ... I thought #5 bypassed the interface

If that is so ... seems like trying to do anything with it on #5 would
be unfruitful

Grady

 

[Stanger007]

I've never tried it myself ... but ... I thought #5 bypassed the interface

If that is so ... seems like trying to do anything with it on #5 would
be unfruitful

Give it a shot and report back what you find.

This is how I started my initial tune way back when! Something has gone screwy since then, however.

Wes

 

[Mustangless]

I have to put a thin piece of cardboard between the eec and tweecer for mine to work right. Maybe you should try that.
http://www.fordfuelinjection.com/images/chip05.jpg
found this picture on here. See the white foam between it?

 

[final5-0]

Give it a shot and report back what you find.

This is how I started my initial tune way back when! Something has gone screwy since then, however.

Wes

I would be willing to help
but
I got him down for a while

Maybe some other member would get involved here for help

Grady

 

[Stanger007]

I would be willing to help
but
I got him down for a while

Maybe some other member would get involved here for help

Kenne Bell???

Good call on the spacer, Mustangless. I taped on a piece of welding rod that was just the right size to fill the gap.

Wes

 

[sn-95matt5-0]

i didnt install a spacer so that may be wats wrong with it. as soon as i get a chance i will put a piece of carboard or something in it.

 

[blksn955.o]

are you saying #5 as in the "off" or the opposite end of the dial?

I have been running my tune on the slot furthest away from the "off" setting. If that one is #5 then its good on mine.

 

[Stanger007]

The last time I tried to do a stock read, I also got the same problem. Tried it again yesterday and still getting odd #s. This is with CalEdit *OR* BinaryEditor.

It is not a huge deal for me, as I have the stock tunes already, but I can verify that it did work waaay back when I first got the twEECer.

Thread back from the dead.

I am a moron - there is a "Read Ford" button in both CalEdit and BinaryEditor. That will read the tune from the PCM regardless of what switch position the chip is in.

Sometimes it's the simple things that get ya...

Wes

 

[sn-95matt5-0]

i added a spacer and my tweecer is working perfectly now. now i just need to figure out wat to change with it i'm still trying to find my detonating problem

 

[final5-0]

i added a spacer and my tweecer is working perfectly now. now i just need to figure out wat to change with it i'm still trying to find my detonating problem

A method of reducing spark

If you can duplicate the ping thing at will ........

Just get all setup to datalog and choose the capture option

As soon as you hear the ping, kill the capture rate.

You will know the event was just before the end of the data

Look at the load to see where it falls in the table and adjust accordingly

btw ... knowing your fuel ratio is important as well but you need a wb
if we are talking about ping at WOT.

Grady

 

[Stanger007]

BinaryEditor has a cool feature while datalogging, just hit the "Control" key to start tagging rows and hit it a second time to stop tagging rows. Each time you start the tagging, the rows are marked with an incrementing number... pretty handy!

Wes

 

[sn-95matt5-0]

yeah its ping at WOT and it only happens when the motor is warm

 

[final5-0]

BinaryEditor has a cool feature while datalogging, just hit the "Control" key to start tagging rows and hit it a second time to stop tagging rows. Each time you start the tagging, the rows are marked with an incrementing number... pretty handy!

Wes

I've found on my dataloggs I can hit the space bar and it will stop
the capture

The tagging feature on BE sounds really nice

Grady