tweecer peeps..breakpoint input question

[blksn955.o]

I posted on the tweecer forums but they have been realy slow lately with who is on and who isnt (mostly the isnt part),

I cannot get my T4M0 breakpoint to enter into the j4j1 program, or vise versa. I get some .00013xx number. I forgot how your supposed to enter it to get it to read correct.

thanks.

posted this in talk also, didnt notice I was in talk until I came back..if a mod could remove that post it would be great...thanks again.

 

[final5-0]

Greg

Mine is entered as 1.9878e-5

The e-5 means the d point is 5 places to the left or .000019878

CalEdit is looking for the e-5 method of notation however.

Grady

 

[blksn955.o]

Thats how I am entering it???

counting 6 spaces for the dec. forward. the breakpoint on the stock T4M0 is 9.98378E-6. I enter 00000998378, and have tried .00000998378 when I switch to tables and go back it is like .00013xxx? Do I have to move it E-5 for the j4j1 or is there something else wrong?

Thanks Grady

 

[final5-0]

Thats how I am entering it???

counting 6 spaces for the dec. forward. the breakpoint on the stock T4M0 is 9.98378E-6. I enter 00000998378, and have tried .00000998378 when I switch to tables and go back it is like .00013xxx? Do I have to move it E-5 for the j4j1 or is there something else wrong?

Thanks Grady

I looked at a couple of t4m0 files and the value I saw was 1.0014e-5.

The value you show of .00000998378 would be .998378e-5.

Try the value of .9984e-5 and see if CalEdit takes it.

Grady

 

[blksn955.o]

hmmm that is wierd???

my t4m0 file has 9.98378E-6

my j4j1 has the 1.00136E-5

if the eec is "rounding" to its nearest value then the 1 makes sense and would be logical.

maybe its a variance of some kind in my t4m0 bin file.

Thanks again for the help

 

[blksn955.o]

entered it in as .00000998378 in the j4j1 (e5), it came back as 9.98378E-6

 

[Zero Signal]

It's e-5 moving the decimal like that is a huge change. You'll never get it outside e-5 you will usually use between 1 and 3e-5

 

[blksn955.o]

it did the e6 on its own.

The only way I can get it to read e-5 is if I do it .0000998378 and that is not close to the value of E6. then it reads 9.98378e-5 when the stock value is 9.98378e-6 (in the t4m0 factory tune)

9.98378e-6 is = to .998378e-5

Grady- is that 1.0014e-5 what your bin is showing stock? Might try that breakpoint. The only thing is my stock j4j1 breakpoint is 1.00136 and that tune has the poor perf. issues.

 

[final5-0]

Grady- is that 1.0014e-5 what your bin is showing stock? Might try that breakpoint. The only thing is my stock j4j1 breakpoint is 1.00136 and that tune has the poor perf. issues.

I looked at t4m0, j4j1, & u4p0 ... they all had the value of 1.0014e-5

Grady

 

[blksn955.o]

do you think I have a bad set of bin files or do you think the diff. is in the 1.20 v 1.3 version I use?

They are deff. diff. on my computer.

I will input the 1.0014 and see what it does, load one tune up and datalog and load the other and datalog.

 

[bjl95mustang]

Is your software set to cbaza? if it's set to another one it will act wiered.

 

[Zero Signal]

Yeah mine was 1.0014e-5 ish stock. By the way, how is your combo working out so far despite not having the tune finished? Just wondering sinde it's close to what I'm doing.

 

[blksn955.o]

Is your software set to cbaza? if it's set to another one it will act wiered.

yes set to cbaza.

 

[blksn955.o]

Yeah mine was 1.0014e-5 ish stock. By the way, how is your combo working out so far despite not having the tune finished? Just wondering sinde it's close to what I'm doing.

I am still sorting out issues, need to redo my valve train as I need the correct pushrods (still on the stockers) and they are way to long. I am sure that is hurting me, how much I dont know. Drivability has been great so far with the tweecer just the perfrom totaly sucks, runs like it did with the stock long block.

I think I am going to input the 1.0014e-5 and see, if everyone else has that fig. in all the tunes.

I also think I am going to download a new stock j4j1 and t4m0 bin file, might have a bad bin base file.