LB7: Question on changing RPM signal..

[weazel]

Can the ESS (RPM) signal be changed with efi live in an lb7 ECM? Everything but my tach works correctly in my conversion. I'm hoping it can be versus purchasing a pricey signal changing box..

This is an 03 lb7 ECM in my 88 Chevy conversion. Gauge cluster is out of a 93 v8 equipped vehicle.

 

[THEFERMANATOR]

No was the last word I got from efilive when I asked about it. I'm assum8ng you're using a gas tach as the diesel one works off the alternator. You have 2 options, either you can buy a tach adapter, or you can recalibrate your v8 tach for a 4 cylinder. Most likely the adapter is cheaper unless you have some patience, good soldering tools, and a signal generator of some sort. I'm set up to do them, but in all honesty, a conversion box would be cheaper than shipping it to somebody and the hours labor to change the resistor to recalibrate the tach.

 

[weazel]

Ok, not what I was hoping to hear, but at least it's a definite answer. Thanks for the info!

 

[THEFERMANATOR]

Heres where I asked about it before. Maybe you could try asking as well. I bought the stuff to recalibrate mine as the cluster I'm going to has a 6K rpm tach and I only want a 5K rpm one. Between that and the half the number of pulses signal, I decided to set up to recalibrate it.
https://forum.efilive.com/showthread.php?26265-Tachometer-tables

 

[weazel]

Thanks for the link, I went ahead and posted in there also. Hopefully they will find something out for us to use tuning wise versus having to go through all the trouble of wiring in a box or having to redo the cluster...

 

[THEFERMANATOR]

Here was the cheapest conversion bos I found for the tach. Won't work for me because of all that I'm doing.

http://www.bakerelectronix.com/products_tsd/

 

[weazel]

Oh now those are affordable! That's probably the route I'll take, since efi doesn't want to "waste their time" with the old stuff...

I wasn't too thrilled with the response on the efi forum..

 

[duratothemax]

Oh now those are affordable! That's probably the route I'll take, since efi doesn't want to "waste their time" with the old stuff...

I wasn't too thrilled with the response on the efi forum..

Well its easily a DOZEN OR MORE HOURS' worth of work to go back through the ECM code and figure out the tach signal stuff. To satisfy the needs of TWO people for an 8 year old platform? And you expect all that for free? Come on...

Do YOU want to pay them for their time to figure it out? Guarantee it would cost you a helluva lot more than an "expensive" signal box.

Ben

 

[weazel]

Never know man, maybe I would...

 

[EFI Support]

Oh now those are affordable! That's probably the route I'll take, since efi doesn't want to "waste their time" with the old stuff...

I wasn't too thrilled with the response on the efi forum..

We never said it was a waste of time, what we said to you was...

LLY calibrations were last updated in October 2008, almost 8 years ago. The amount of time our developer would need to spend to get back up to speed on that controller, then see if the calibrations existed, followed by internal testing and beta testing to ensure the calibrations continued to operate correctly would make the task not viable for 2 requests in 8 years, sorry.

Well its easily a DOZEN OR MORE HOURS' worth of work to go back through the ECM code and figure out the tach signal stuff. To satisfy the needs of TWO people for an 8 year old platform? And you expect all that for free? Come on...

Do YOU want to pay them for their time to figure it out? Guarantee it would cost you a helluva lot more than an "expensive" signal box.

Ben

The development is the 'easy' part of the equation. Looking and adding the code takes the least amount of time. I'd estimate 10-15 hours for this task, then another 5 hours to import that data across all operating systems.

The biggest time consumer is the internal checking that every operating system continues to operate in the same fashion that it did before it was edited. We'd expect that we'd need to spend between 5-7 hours per operating system in internal checking, and then once released another 5-10 hours with adhoc support queries for the changes made.

So that would be 20 development hours, 30 checking hours, and another 5 development support hours.

You tell me if a minimum of 50 development hours for a programmer is an efficient use of time for a platform that hasn't been modified in 8 years with only 2 customer requests?

To assist customers in platforms where additional parameters need to be added where it's not viable for us to do so, EFILive added the ability for users to add these. This obviously requires very detailed knowledge, but the function exists.

If you don't have the skills to add it, perhaps you can find a programmer than can for less than cost of the device ($40) THEFERMANATOR linked you to.

Cheers
Cindy

 

[weazel]

Oh, I'm sure I could. But like you guys, I don't have the time. I was excited hoping it could be done, but the response that was written suggested to me it more or less was a "waste of time."

And yes, that was a fancy way of saying, waste of time.. That's fine with me if you guys don't want to do it. seems like a few of you are getting bent out of shape just because I stated my opinion of how this turned out. I wasn't thrilled. Yep it's true I wasn't. Oh well life goes the ef on. It's like you guys going to the store for something you've been thinking about getting all day, been anticipating to get that part, or food, or hell even beer.. But ya get there and there is none and the store says we aren't going to carry it and don't want to take the time to get any more of said product. You wouldn't be thrilled either, right? Just simply what I was saying.

just cuz y'all aren't going to add the rpm signal change option doesn't mean I'll be bad mouthing efi or quit using their products.

And FYI, yes I will be using one of the modules Ferm so kindly, and helpfully linked in here as that is more along the lines of what I was after if efi didn't or couldn't Help in that part of tuning. :thumb::thumb:

 

[zf>allison]

Oh, I'm sure I could. But like you guys, I don't have the time. I was excited hoping it could be done, but the response that was written suggested to me it more or less was a "waste of time."

And yes, that was a fancy way of saying, waste of time.. That's fine with me if you guys don't want to do it. seems like a few of you are getting bent out of shape just because I stated my opinion of how this turned out. I wasn't thrilled. Yep it's true I wasn't. Oh well life goes the ef on. It's like you guys going to the store for something you've been thinking about getting all day, been anticipating to get that part, or food, or hell even beer.. But ya get there and there is none and the store says we aren't going to carry it and don't want to take the time to get any more of said product. You wouldn't be thrilled either, right? Just simply what I was saying.

just cuz y'all aren't going to add the rpm signal change option doesn't mean I'll be bad mouthing efi or quit using their products.

And FYI, yes I will be using one of the modules Ferm so kindly, and helpfully linked in here as that is more along the lines of what I was after if efi didn't or couldn't Help in that part of tuning. :thumb::thumb:

I might look at a box as well to slow down the signal so my bd limiter can maybe work like advertised.

 

[weazel]

I'm really liking the ATSD version they have listed. I'm probably going to use that one versus the other two listed..

 

[EFI Support]

Oh, I'm sure I could. But like you guys, I don't have the time. I was excited hoping it could be done, but the response that was written suggested to me it more or less was a "waste of time."

And yes, that was a fancy way of saying, waste of time.. That's fine with me if you guys don't want to do it.

I'm sorry you took our response as a waste of time, it wasn't intended to come across that way. Development is our business. The income that generates pays for the food we put on the table and the roof over our head - it has to be timely and make economic sense. I don't think you'll find many businesses that could support 50 development hours for a $125 license fee for both you and Ferm.

Cheers
Cindy

 

[THEFERMANATOR]

They're alot cheaper than dakota digital's box. Or you can run a diesel cluster as they trigger off the alternator. I looked into the box myself, but for my use, it didn't make much sense. I'm wanting to go to an ESCALADE cluster for the 120 speedo, but I'm going to get a custom gauge face to retain all the diesel only warning indicators and go from the 6K RPM tach to a 5K RPM tach as I'm beyond OCD about little details like that. So I have to not only convert from a v8 to 4 cylinder, but also correct for the different RPM range. So for me, it made more sense to recalibrate the actual cluster by either going to an adjusteable reostat, or just find the correct resistor and swap it out.

 

[duratothemax]

We never said it was a waste of time, what we said to you was...

LLY calibrations were last updated in October 2008, almost 8 years ago. The amount of time our developer would need to spend to get back up to speed on that controller, then see if the calibrations existed, followed by internal testing and beta testing to ensure the calibrations continued to operate correctly would make the task not viable for 2 requests in 8 years, sorry.


The development is the 'easy' part of the equation. Looking and adding the code takes the least amount of time. I'd estimate 10-15 hours for this task, then another 5 hours to import that data across all operating systems.

The biggest time consumer is the internal checking that every operating system continues to operate in the same fashion that it did before it was edited. We'd expect that we'd need to spend between 5-7 hours per operating system in internal checking, and then once released another 5-10 hours with adhoc support queries for the changes made.

So that would be 20 development hours, 30 checking hours, and another 5 development support hours.

You tell me if a minimum of 50 development hours for a programmer is an efficient use of time for a platform that hasn't been modified in 8 years with only 2 customer requests?

To assist customers in platforms where additional parameters need to be added where it's not viable for us to do so, EFILive added the ability for users to add these. This obviously requires very detailed knowledge, but the function exists.

If you don't have the skills to add it, perhaps you can find a programmer than can for less than cost of the device ($40) THEFERMANATOR linked you to.

Cheers
Cindy

I WOULD really love the VATS-disable for LML to be re-visited though.

It would certainly make a lot of standalone customers happy; having to keep the BCM, theft deterrent module, and factory transponder key hooked up for engine swaps is a huge pain. Ive had to turn away a dozen or more standalone harness jobs just because its too time consuming and not profitable enough for me to do LML standalone harnesses.

But thats another discussion topic for another time.