Possible GReddy/eManage behavior?
03-21-2005, 02:14 PM
#1
Where the air is rare
Thread Starter
Possible GReddy/eManage behavior?
I started discussing this in the "Greddy Turbo Installed" thread, but will recap here.
I have had the Greddy turbo installed for a few weeks, and had no real issues. At least none worth mentioning. This weekend I noticed what sounded like detonation in the 4K range, which I hadn't noticed before. Since I now had my Support Tool and cable, I foolishly decided to load a configurable map in the eManage, and fix my detonation issue.
My eManage reported firmware version 1.42...the version which has been reported to work only on the "Gold" eManage units. From reports, the Gold units are not in general release in the US , and required version 1.20+ of the support tool software to operate. My laptop had version 1.13 of the support tool software installed, and appeared to have no problem communicating with the unit and reading the available realtime information from the locked eManage unit.
I decided to install the "stock" map Jon received from Greddy for the RX-8 kit. I committed to clearing out the existing "locked" map. At this point, the software reported a "communications failure". I tried several resets, restarts and maps, nothing could be successfully read or written to the unit. I finally solved the problem by creating an English/Japanese hybrid version (1.24) of the support tool software. I was then able to read, write and compare maps with the unit. The only notable downside was that the menus were displaying "blocks" instead of text, because one of the resource DLL's was in Japanese.
After loading the stock Greddy map, I took the car for a spin. I noticed some stumbling and excessively high idles at stop signs. After several seconds, it would settle down to the normal 850-900RPM idle (I was watching the laptop realtime values, for the most part). It wasn't until I pulled in to my driveway that I noticed that during the "fast idle" period, the temperature gauge was reading dead cold. I decided to let things cool down overnight and check all the connections in the morning.
Sunday morning I pulled the air valve and blower to get a good look at the ECT (Engine Coolant Temperature) sensor. The sensor and connection appeared undisturbed and securely plugged in. I buttoned everything up, and double checked all visible connections and hoses. I cannot identify any electrical issues, but I may do a continuity test from the ECU if the situation warrants it.
Basically, my situation appears to be this: whenever the engine accelerates (or moderately revved) the temp gauge will go dead, and return to life several seconds later. During the dead time, the cold-engine enrichment and fast idle occurs.
So, my question is: what relationship is there between the eManage map and the ECT and/or temperature gauge? Why did this only occur only AFTER loading a new map?
eManage=1.42 (as delivered)
Support Tool=1.24 (Eng/Jap hybrid)
Map="stock" Greddy map
Any help or suggestions are welcomed...
I have had the Greddy turbo installed for a few weeks, and had no real issues. At least none worth mentioning. This weekend I noticed what sounded like detonation in the 4K range, which I hadn't noticed before. Since I now had my Support Tool and cable, I foolishly decided to load a configurable map in the eManage, and fix my detonation issue.
My eManage reported firmware version 1.42...the version which has been reported to work only on the "Gold" eManage units. From reports, the Gold units are not in general release in the US , and required version 1.20+ of the support tool software to operate. My laptop had version 1.13 of the support tool software installed, and appeared to have no problem communicating with the unit and reading the available realtime information from the locked eManage unit.
I decided to install the "stock" map Jon received from Greddy for the RX-8 kit. I committed to clearing out the existing "locked" map. At this point, the software reported a "communications failure". I tried several resets, restarts and maps, nothing could be successfully read or written to the unit. I finally solved the problem by creating an English/Japanese hybrid version (1.24) of the support tool software. I was then able to read, write and compare maps with the unit. The only notable downside was that the menus were displaying "blocks" instead of text, because one of the resource DLL's was in Japanese.
After loading the stock Greddy map, I took the car for a spin. I noticed some stumbling and excessively high idles at stop signs. After several seconds, it would settle down to the normal 850-900RPM idle (I was watching the laptop realtime values, for the most part). It wasn't until I pulled in to my driveway that I noticed that during the "fast idle" period, the temperature gauge was reading dead cold. I decided to let things cool down overnight and check all the connections in the morning.
Sunday morning I pulled the air valve and blower to get a good look at the ECT (Engine Coolant Temperature) sensor. The sensor and connection appeared undisturbed and securely plugged in. I buttoned everything up, and double checked all visible connections and hoses. I cannot identify any electrical issues, but I may do a continuity test from the ECU if the situation warrants it.
Basically, my situation appears to be this: whenever the engine accelerates (or moderately revved) the temp gauge will go dead, and return to life several seconds later. During the dead time, the cold-engine enrichment and fast idle occurs.
So, my question is: what relationship is there between the eManage map and the ECT and/or temperature gauge? Why did this only occur only AFTER loading a new map?
eManage=1.42 (as delivered)
Support Tool=1.24 (Eng/Jap hybrid)
Map="stock" Greddy map
Any help or suggestions are welcomed...
Last edited by JoeMamma; 03-24-2005 at 10:00 PM.
03-23-2005, 11:31 PM
#4
Where the air is rare
Thread Starter
I spoke with Benny today and he solved my problem. 
I confessed to him that I had dumped and reloaded the unlocked map, and explained the odd temperature gauge behavior. Since I had the 1.42 firmware, he said I would need to send the unit back to have the latest map revision loaded. I told him that I had just I fetched the US (english) version (1.24) of the support tool software, so he said that he would send me the new map. After reloading the new map, I took it for a spin and found everything is back to normal, but it is too cold out to determine if I have solved the detonation issue.
Here's what he explained: in order to keep the mid-range from going closed-loop when the program is trying to add fuel, they pull the ECT (temp sensor) to kick it into open-loop, and not try to pull out the extra fuel. It's interesting, because now I can see the temp gauge drop in the mid-range, and pop back as soon as the throttle is released. It then occurred to me that I had thought I had noticed the temp gauge drop before, but never gave it a second thought at the time.
I confessed to him that I had dumped and reloaded the unlocked map, and explained the odd temperature gauge behavior. Since I had the 1.42 firmware, he said I would need to send the unit back to have the latest map revision loaded. I told him that I had just I fetched the US (english) version (1.24) of the support tool software, so he said that he would send me the new map. After reloading the new map, I took it for a spin and found everything is back to normal, but it is too cold out to determine if I have solved the detonation issue.
Here's what he explained: in order to keep the mid-range from going closed-loop when the program is trying to add fuel, they pull the ECT (temp sensor) to kick it into open-loop, and not try to pull out the extra fuel. It's interesting, because now I can see the temp gauge drop in the mid-range, and pop back as soon as the throttle is released. It then occurred to me that I had thought I had noticed the temp gauge drop before, but never gave it a second thought at the time.
Thread
Thread Starter
Forum
Replies
Last Post
