Notices
Vishnu Performance - California [Visit Site]

Xede - maps aren't same error message

 
Thread Tools
 
Search this Thread
 
Old Apr 25, 2006 | 09:57 PM
  #1  
EVOlved in PDX's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 27
Likes: 0
From: Portland, Oregon
Xede - maps aren't same error message

Ever since I upgraded to V3.2 on my Xede, my car runs very different. Looks like it is back to the dyno.
However, can somebody tell me about this "Warning" message I keep getting when I try to edit a few maps - "The maps I am editing are not the same as the ones in Xede.", which I can choose to ignor, write maps, etc.
I have downloaded, uploaded, burned, etc. but get this message every time I download a map to begin editing. What gives?

Also, does ANYBODY know about this output scales feature? I don't know how to accomodate for my bigger injectors or MAF intake against my maps. My CEL is always on with a V390 Vishnu standard download map. I am running rich and have idle trouble..
Old Apr 25, 2006 | 10:09 PM
  #2  
jj_008's Avatar
Evolved Member
iTrader: (8)
 
Joined: Nov 2003
Posts: 2,064
Likes: 0
From: Salem, OR
The error is a bug in the software. Just ignore it. Do not use the scaling feature for your bigger injectors. You need to send your ECU to Vishnu for a reflash. Or you could put your stock injectors back in and save yourself $100.
Old Apr 26, 2006 | 10:00 PM
  #3  
EVOlved in PDX's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 27
Likes: 0
From: Portland, Oregon
But I thought that is what the Xede's purpose was - to not have to reflash the ecu, and have full control over ECU response. Am I missing the point of having an Xede? The Xede help talks about using the output scaling for such things as bigger fuel injector - rather than alter a map by hand, apply just a single variable to the whole map. I like this concept.
I need help with this thing - or do I head for the Dyno?
Old Apr 26, 2006 | 10:12 PM
  #4  
jj_008's Avatar
Evolved Member
iTrader: (8)
 
Joined: Nov 2003
Posts: 2,064
Likes: 0
From: Salem, OR
Originally Posted by EVOlved in PDX
But I thought that is what the Xede's purpose was - to not have to reflash the ecu, and have full control over ECU response. Am I missing the point of having an Xede? The Xede help talks about using the output scaling for such things as bigger fuel injector - rather than alter a map by hand, apply just a single variable to the whole map. I like this concept.
I need help with this thing - or do I head for the Dyno?
The XEDE doesn't control closed loop fueling (at least not in regards to injector scaling on an EVO). In order to get your car to idle and cruise at the proper AFR you need to get a reflash to scale the injectors.

The output scaling works for bigger injectors in open loop fueling. I recommend putting the stock injectors back in. The stock injectors will work for anything the stock turbo can put out.
Old Apr 26, 2006 | 10:57 PM
  #5  
Noize's Avatar
EvoM Administrator
20 Year Member
Liked
Loved
Community Favorite
iTrader: (24)
 
Joined: Mar 2003
Posts: 8,849
Likes: 138
From: Franklin, TN
From what I've seen, the cause of that error message is not a software bug, but a hardware bug. Most modern laptops use USB and have no serial cables. There are several serial to USB adapters on the market, but a lot of them don't work. There are a few (like the NewEgg one that I have) that work sometimes, but lose communication with the XEDE. When I get that message, I re-upload the map I'm working in to the XEDE to be safe.

FWIW, I've never had a laptop with a direct serial connection ever get this error message.

Cliff's notes: I think everything will be okay, just make sure you select the option to uload your current changes to the XEDE before you burn the changes to the eeprom if you've received that message. It is an extra step, but good insurance to make sure your changes write when the software shows that error.

Last edited by Noize; Apr 26, 2006 at 11:01 PM.
Old Apr 27, 2006 | 01:12 PM
  #6  
EVOlved in PDX's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 27
Likes: 0
From: Portland, Oregon
What is the difference between closed and open loop fueling? I am a newbie at this, but along with my Xede, 660 injectors - I also have all the vishnu upgrades minus the bigger turbo. I have the cams, gears, intercooler, hks intake, turbo back with test pipe. I even have had head machining done. It does idle, you know - lopy. After a hard run at WOT, push the clutch in and it may stall sometimes.
Do I really need to find out if my ecu has been flashed? Why do people buy both the Xede and a flashed ecu?
Old Apr 27, 2006 | 01:36 PM
  #7  
donour's Avatar
Evolved Member
iTrader: (6)
 
Joined: May 2004
Posts: 2,502
Likes: 1
From: Tennessee, USA
Originally Posted by EVOlved in PDX
What is the difference between closed and open loop fueling? I am a newbie at this, but along with my Xede, 660 injectors - I also have all the vishnu upgrades minus the bigger turbo. I have the cams, gears, intercooler, hks intake, turbo back with test pipe. I even have had head machining done. It does idle, you know - lopy. After a hard run at WOT, push the clutch in and it may stall sometimes.
A closed loop system (any control system) uses feedback to adjust the output. Closed loop fuel systems use an O2 sensor to trim the amount of fuel injected to a certain air/fuel ratio. Because the stock O2 sensor is narrowband, it is really only accurate around stoichiometric (ie low load and idling). When the engine goes under heavy, load the ECU no longer attempts to trim fuel with the O2 signal. Instead it just feeds fuel according to the air flow (MAF reading).

Do I really need to find out if my ecu has been flashed? Why do people buy both the Xede and a flashed ecu?
EDIT: oops, I missed the question. People reflash the stock ECU to raise the rev limiter, remove the boost cut, remove the speed limit, and scale the stock map for different sized injectors. The Xede can't do any of those things.

d

Last edited by donour; Apr 27, 2006 at 01:44 PM.
Old Apr 27, 2006 | 02:54 PM
  #8  
Ludikraut's Avatar
Evolved Member
iTrader: (17)
 
Joined: Apr 2004
Posts: 6,224
Likes: 0
From: 41° 59' N, 87° 54' W
Yes, you should find out if your ECU has been flashed. I assume that you bought the car used, yes?

I would personally find out exactly which injectors Shiv is scaling for. If they are not the same as yours (i.e. brand, model, and cc), then I would advise taking the time to actually bring your car to a shop that can reflash it on a dyno. That way your injector scaling and idle issues can be addressed all in one shot.

The aren't many reasons to have a fully flashed ECU and the XEDE. Most XEDE users only ever need the XEDEflash, which is what Donour is referring to in his post above. If you have a setup that is outside of the normal Vishnu upgrade path, then you may consider a full ECU flash on top of the XEDE ... which is what I will be running.

l8r)
Old Apr 27, 2006 | 04:21 PM
  #9  
EVOlved in PDX's Avatar
Thread Starter
Newbie
 
Joined: Apr 2006
Posts: 27
Likes: 0
From: Portland, Oregon
Yes the car is used. I will find out if the ECU has been flashed. What if you buy a wideband O2 sensor? Also, since car runs rich, should the O2 sensor be cleaned? Does it sit in the exhaust somewhere? Is this why there may be a ServiceELight on?
Old Apr 27, 2006 | 04:30 PM
  #10  
Ludikraut's Avatar
Evolved Member
iTrader: (17)
 
Joined: Apr 2004
Posts: 6,224
Likes: 0
From: 41° 59' N, 87° 54' W
You cannot really clean your O2 sensors. If the car has a HF cat or no cat, then you will most likely get a code P0420 CEL (Check Engine Light). Go to autozone and have them pull the CEL to see which code it is.

A wideband O2 sensor will allow you to monitor what your air/fuel ratio (AFR) is at. It won't fix anything by itself, it's just a tool to help you figure out what is going on with your car.

l8r)
Old Apr 29, 2006 | 03:57 PM
  #11  
Jorge T's Avatar
Evolved Member
iTrader: (18)
 
Joined: May 2004
Posts: 1,494
Likes: 1
From: Houston, TX
...the error also happens with a direct serial connector



Originally Posted by Noize
From what I've seen, the cause of that error message is not a software bug, but a hardware bug. Most modern laptops use USB and have no serial cables. There are several serial to USB adapters on the market, but a lot of them don't work. There are a few (like the NewEgg one that I have) that work sometimes, but lose communication with the XEDE. When I get that message, I re-upload the map I'm working in to the XEDE to be safe.

FWIW, I've never had a laptop with a direct serial connection ever get this error message.

Cliff's notes: I think everything will be okay, just make sure you select the option to uload your current changes to the XEDE before you burn the changes to the eeprom if you've received that message. It is an extra step, but good insurance to make sure your changes write when the software shows that error.
 




All times are GMT -7. The time now is 03:04 AM.