Hey all. I need some help with the basics on emanage. I'm helping out a friend who just got an emanage (but lacks Internet @ home).

He just got the blu emanage with the support cable & cd. What's involved in physically installing this unit? He got it used. Should we need to wipe out any previous maps? Is there a 'stock' map to work with? He only has a couple mods (o2 housing, dp & exhaust). Also, I heard something about coil packs fying? What's this about?

Anything I/we need to know on this? I'll be doing most of the tuning (that part I understand), but I haven't dealt with the emanage on an Evo.

Thanks in advance.

 

the coil packs frying are for the ignition harness... i am having alot of success with just the injector harness and pocket logger

 

There is a fair amount of info in this forum about the coil pack problem. Unfortunately it's not very conclusive. I have had the ignition harness installed for 2 years now without issue. You don't want to use any existing maps, who knows what they were built for. I wrote an emanage install vfaq, look for it in the Evo How-to section.

 

I found that in my searches. Good write up. We'll definately be using it.

It turns out that the emanage is brand new. The person he got it from decided to go another route. So its blank. Can it be run with out any map on it? Just curious if we can get it installed and then tune it the next day.

 

Running it with no maps is just like running a S-AFC with everything zeroed out - no changes will be made so the car will run like stock.

Where are you at in Ohio? If you have any problems, let me know and I'll try to help.

 

Ahh that's good news. I was hoping to not have to rush on this if we ran outta time.

I'm in Centerville; just south of Dayton. I didn't even realize you're from Cincy.

 

So can I leave the ari flow adjustments alone? Do I need to mess with those on the the initial setup?

 

So I got the e-mange wired in. Thanks for your vfaq... Very helpful. Got a few Q's/probs..

1. I can't update the unit. We set the key to ON, open the support tool, click on update main unit and it errors out. Says the communication fails. But it says "online" on the tool. It also turns off the active led (from the red, green blinking status). I updated to 1.25 of the support tool and it still does it. Any ideas?

2. The car idles about 350-400 rpm higher than normal. It also throws a MIL, P0102 (MAF voltage low). Is this because the tool isn't updated or adjusted? I saw that you have to calibrate the throttle position.

So for now I just hooked his MAF wire back up and removed the e-manage.

 

What kind of cable are you using to connect the emanage to the laptop? Most communication problems can be traced back to the cable. The emanage is very picky in this regard. Also I'll have to check to see if 1.25 is compatible with a regular blue emanage. I am running 1.25, but I have hacked my emanage to gold status.

The high idle is a result of the low MAF voltage. Could you have the MAF in/out hooked up backwards? If all the maps are zero'd out (default on a new unit), the car should run exactly as stock.

 

make sure your pins are correctly adjusted inside and outside the unit... if you don't have the english instruction manual, you can download it off the yahoo groups..

i had the blue emanage unit on my car, i would go dynoflash until your warranty is up and then go EMS... i didn't like that it couldn't datalog nor view knock... at least i couldn't get it to...

 

No piggy back, save the S-AFC II logs knock, and even that isn't a true knock reading.

 

We're using the Greddy support tool cable -> rs232/usb adaptor. I read on the yahoo emanage group that sometimes the update won't work with windows xp. Just another sign of crappy programming on their part.

We have the light blue wire from the e-manage going to the red/white wire coming from the ECU wire loom/harness. The other wire is going to the red/white wire on the ECU connector. Is this right??

Thanks for the advice so far. My friend is on his way back to my place now.

 

Well we still couldn't get it to cooperate. Either tonight or tomorrow we'll be trying it with Windows 2000 & Windows 98SE. Maybe that will do it.

 

Sounds like it is wired correctly, what usb adaptor cable are you using? See if you can try it on a computer that has an actual serial port. The serial to usb cable is where most of the communication errors come from. I picked up my cable from Radio Shack - I'll see if I can dig up a part number. I'm using XP by the way...

 

I've got an oooold laptop that we'll be trying out. Maybe it will work.

The adapter I have is I/O magic and I know it works well. I use with my diag software I wrote as well as countless switches & routers at work.