DSMTalk Forums: Mitsubishi Eclipse, Plymouth Laser, and Eagle Talon Forum banner
1 - 6 of 6 Posts

luizdiefenbach

· Registered
Joined
·
50 Posts
Discussion starter · #1 ·
Hi I know that 2g knock sensors can't be directly used on 1g ecus.
But the 2g KS is a better unit than 1g and probably many will benefit from the 2g sensor in 1g.
I also know that AEM guys use the 2g sensor but thats in EMS stand alone.

The question is: has anybody made a adapter for the 2g KS?
its too difficult to make the 2g sensor simulate the 1g?
Maybe we could do this with very little and cheap electronic components.
any ideas?
 
luizdiefenbach said:
Maybe we could do this with very little and cheap electronic components.
any ideas?

A box such as you describe would most likely not do anything because the code that "listens" to the sensor and determines what is knock and what's just noise is inside the ECU. This is why the AEM works with the 2G sensor, you have to calibrate the ECU with a knock table yourself. Possibly, an option would be for someone like DSMlink or Keydiver to incorporate a code change into their chips to allow for 2G sensor use on a 1G. It might be worth asking them about if there was enough interest.
 
Discussion starter · #5 ·
But the KS don't have any "eletric" incompatibility? more resistance / other signal type / work with another voltage, etc?
I really think that a good knock feedback sistem is something to consider.
Some os dsm are prone thoi the phantom knock problem and some of them really have a hard time to get rid of this false knock count.
Maybe using the 2g KS sensor can help those dsmers.

If someone have info on Knock sensors signals it can be a begginning for adapting the 2g sensor in 1g
 
You're missing the point. Let's say theoretically you built this conversion box. All it would be doing is dumbing down the more linear 2G sensor's signal so that it emulates the all-or-nothing 1G signal. That's the only way a 1G ECU would recognize it. It wouldn't accomplish anything, the 1G ECU's knock table is still exactly the same. Phantom knock is easily fixed with DSMlink or Keydiver. When multiple solutions already exist for a problem, there's really no need to try and invent a less effective solution.
 
1 - 6 of 6 Posts