I was gonna put this in the Emanage forum...but it appears not to many people look at that . Anyway, I have been doing sum data logging with the support tool and it seems to be a little wacky. For the most part, it appears to be reading what it should, or at least around what it should in accordance w/ my map I have been playing around with. But, at sum points it's telling me I hit 13k rpms!!!! It is saying my duty cycle is maxed out there. Logically, one would think 13k would max out a duty cycle under sum kind of boost, but this car or none I can think of will see 13k rpm! But, at other points, it reads what it should. Any1 else get bizzar readings when datalogging with the support tool??

 

the haltech e6x does stuff like that. ignition interference, rfi, emi, plugs, wires, noisy alternator, etc...

go over your harness and connections. check the plug wires, etc... maybe even try unplugging your alternator for a run or two and see if the problem goes away.

 

emanage cant pick up rpm worth a damn...

 

I ordered the interceptor, but untill I get it in I would like to play around with this more. Its straight for the most part, I got my afr between 11-11.5 mostly, but the few spots where it boggs to 10's and above where it will extend past 12 are the spots I'm having trouble fixing when I data log cus it's not recording where this stuff is happening accurately. At least I'm learning sumthing.

 

This is the result of your acceleration map altering the rpm signal. I had exactly the same issue. Where you hit max rpms, if you look, you accessed high cells in the accel map. Make all the numbers in that map zeros and this should go away. It did for me. I have a post or two on this issue here. Check it out.

 

Thanks alot man, I'll definitely look into that. Did u notice any other results from this as well?

 

The other issue is the RPM dongle. Since it is wired to the leading coils only, it does weird things. I had problems with that on another member's car a few weeks ago.
Sporadic "maxing" of the RPM range, which yeilds odd fuel calculations.

 

But I guess the other ? is, is it no really maxing out the injector cycle when it reads those whacky numbers, b/c they are not real? Or, does it max out the duty cycle b/c it thinks it is what it is supposed to do?? Cus, sumtimes at like 5 pr 6k it will read say 60% total injector cycle, but at 4kish I've noticed only on sum pulls it is maxing it out only for like a second, and then 500 rpms later it's back down to 50%. Kinda hard to obtain reliable data. The most boost I run though is 7 pounds, and I dn't get it up there too often, so I think I'm ok.

 

Yeah, so the idea of the accel map is to read the rate of change of your tps and if it breaches a certain threshold (the units of which I haven't figured) it multiplies your current rpm by a scalar and gives the altered data to the emanage to use as data for the fuel mix. So, in general, when you stomp on the pedal there is a little lag getting all the fuel where it needs to go. This causes a map independent lean spike. This extra rpm signal allows the emanage to add more fuel to eliminate the spike; however, the way my map was configured was so much overkill that my car would bog. I dont seem to get the lean mix on quick throttle changes so I just got rid of the map with all zeros.

MM is right though, about 5% of these spikes appear not to be accel map related, But they are much much reduced without the accel map.

For instance, i would get 3 to 5 spikes on each wot run!!! Without the map, I only see a single rpm spike about once every 5 runs.

 

The acceleration map works by adding the indicated percentage to the existing additional injector map for the indicated time during abrupt throttle change.
It does not fool the RPM.
This is also why it doesn't work with the MAPs that MadDog has provided for the severed injector setup.

 

That makes more sence, but doesn't explain the data. If you track cells using the support tool for runs while the accel map is on, you see rpm spikes concomminant wiith accessed cells in the the accel map with non-zero entrys. When you make the accel map zero, you dont get any spikes.

Furthermore, you dont see these rpm spikes on the E-01 graphical output, only on the emanage support tool data, AND in the subinjector map as tracked cells at the highest rpm (both with the support tool and read with the E-01.) This indicates that the emanage is internally seeing a rpm signal different than what the direct output of the rpm dongle is sending, as shown by the correct E-01 rpm data.

 

Actually, I don't get these spikes often, but they are tied to my ignition setup. They happen even with the acceleration map de-selected.

Actually, my E-01 shows them when they occur.
I think we are experiening different issues.

 

Possibly. I may be experiencing MM's issues, b/c when I got rid of the accel map, I still had some RPM Spikes. They weren't as extreme, but still apparent. It's very difficult to totally know if I actually am maxing out the total injector cycle, or if it just thinks so b/c it thinks I'm at 12k! Like I said, when it's reading normal rpms, the injector cycle is great. But, everyday I'm getting closer to the interceptor...

 

It is important to realize that these spikes may only exist in the log and not actually be represented at the injectors themselves.
The only way to know is to log the actual injector duty cycle (you can tap in injector wire and run it to one of the pulse inputs on the E-01) and compare it to the Support Tool log.

 

Right...That's why it's very difficult to judge whats happening properly.

 

I had this problem before and got solved by adding a PNP transitor along with some diodes to extract the RPM. My RPM is very clean after that. The spikes usually happen around those ports opening area and very random, I thought I was the only one is getting those weird noise 'cause I'm using non-shielded long wiring looms.

 

That makes alot of sense about the spikes happening near the ports opening. My spikes are typically around 5500 and 7200 ish. Sounds like a nice solution.