Ben

iTrader: (33)

Really?

My opinion, both professional and personal: You're chasing the wrong thing because you initially mis-interpreted a datalog. If you had any map sensor issue, it was probably a kinked hose between your intake manifold the sensor's pressure inlet. A kinked hose will cause slow reporting of pressure changes. I hate to use absolutes (that's a pressure joke, get it?) but there's really no hardware failure possible that would cause "sometimes" slow pressure readings.

You have continued to not demonstrate your reported failure. Meanwhile you have not removed your video that condemns our product for the failure you can't demonstrate--while at the same time you continue to ask for our assistance, but generally not follow advise.

I'm trying to help you here, our whole company is. As are people on this forum. But I can't continue to hold your hand as you go further down the wrong rabbit hole.

Braineack

iTrader: (62)

I have feeling the map sensor is working properly but you have a mechanical failure that is showing up on the logs and you're misdiagnosing the failure.

Deepstriker

I've been dealing with Matt via email and he has been helpful. I dont see anywhere within this thread that I haven't been following advice or suggestions people have made.

As for your comments, I don't see any helpful advice except for asking me to take down a video. I have tried 3 map sensors. Would you like me to take a photograph of my map sensor setup? There is no kinked hose, its probably as straight as you can get with a hose. Much better than pulling hose through the firewall like the original DIYPNP design is made for.

Yes, I made an error in reading a pressure signal. I deal with gas in pipes all day in my work and forgive me because we use gauge pressure for all our readings. Even if it is reading a map signal, I honestly don't see a suggestion from you for what else to test. On the other hand, Reverant has at least suggested for me to probe the board and see whats going on.

Of course I won't remove my video. There is nothing in this thread that suggests map sensor failure, or any mechanical failure. I have done my compression tests and leak downs, mechanically everything is firing, I have tested my coilpacks and spark plugs, everything checks out?


How do I know this? I had to borrow a Vipec V88 and order a boomslang harness for temporary use. Let me say this, the car runs fine and it is using the same hardware and sensors. Want video proof? This whole thread seems to be about proving ME wrong, which I have expected from the beginning seeing as this board has a high population with Megasquirt users.

If I'm wrong, then please put it plain and simple for me: What should I test and what should I be expecting to see from these tests? Funny thing is that Matt has actually been trying to help me diagnose the board, vs. you seem to be hung up on mechanical,wiring, etc issues.

EDIT: If its not a map sensor failure (seeing as we have tested all 3, and through email DIYAutotune has confirmed what I'm seeing is correct, then what else could it be?

Braineack, I have been running the car successfully these past few weeks using a Vipec. There is no mechanical failure.

As for those being so hung up on the log files and tune file not being uploaded, well they have been attached so please enlighten me. I have nothing to hide with this issue and I think I have showed pretty good cooperation with trying to reply in a timely response. In the attached logs there is a log from going to close to top of 6th, and then the other two are from the trackday that I was logging in the pits.

Although this thread has been useful, I have also been doing my own due diligence and trying to sort this issue out by testing all the individual components.

If there is one bone to pick with DIYAutotune its that there is no phone number to call. If this was my daily driver I'd be pretty frustrated seeing as the car was down for a couple of weeks.

Zaphod

I am no BIG expert by any means - but I a had a look at your tune and compared it with my old DIYPNP tune.

2 things I noticed:

- your Map sample setting at 35 is veeeery low - it will kep you from a very instant reaction. (I think you should be able to set it at ~60 - 70 without any problems

- weird thing is your injector timing (mine is set at -350°) yours at -175 - I am not sure if this could cause strangeness in the map reading?

Another thing when I re-read this thread - looking at your picture:


I would clean the solder spots of the removed map sensor to be sure there is no short of any sort between the spots...

Matt Cramer

I'd really like to see a log of the car running poorly. The logs you posted don't show much in the way of MAP sensor issues. Here's my take on the data logs you posted in detail. I've sent them by email, but wanted to post them here for the benefit of everyone reading this thread.

2013-05-14_23.08.12.msl: There's a small amount of MAP jitter recorded. There is much more at full throttle than at low throttle amounts. This is causing the TPS driven decel fuel cut to activate. My recommendation is to disable TPSdot fuel cut by changing the Decel Fuel Amount in Acceleration Wizard to 100%.

While the MAP noise can be caused by electrical noise, my experience has been that MAP noise that only manifests itself at full throttle is usually caused by turbulence in the intake. Moving the point where the MAP sensor is plumbed up often can reduce this noise.

2013-5-29_15.43.56.msl: The TPS appears to be broken or calibrated wrong; it's reading -17% through the whole log. There is a point where the MAP bounces up at record 657, but with the TPS not reading, that could have been a stab of the throttle.

2013-5-29_17.55.11.msl: No anomalous MAP readings that I can see. I did spot two points where the RPM input lost sync at idle - possibly a flakey CAS - and several points where a bit of noise on the TPS triggered acceleration enrichment, including one at record 700 that caused a dip in idle.

2013-05-29_17.58.33.msl: MAP reading is not manifesting any noise that I see. I did see a couple spots where the overrun fuel cut kicked in for a very short instant that may have made the engine hiccup.

If you are seeing MAP behavior that looks odd to you, please let me know what record number and file, and I'll have a closer look. But I'm not seeing it.

Based on what I saw in the logs, it's possible that I might have seen the start of a CAS problem. However, this is kind of like trying to diagnose a broken bone with X-rays taken before the accident.

Just wanted to repeat this for emphasis. We've spent a lot of time going over the MAP sensor readings, and other than one point that appears to have been a calibration error, I'm not seeing a MAP sensor reading problem. This thing needs to be diagnosed as a whole.

Deepstriker

Since we are posting emails here, this is my response to your last email Matt. I have yet to hear back.

I have to emphasize again: Nothing has changed since being able to run the car on the VIPEC, no change in CAS, coils, injectors, map location, map sensor, TPS.

Zaphod

As it is in fact a DIY unit I would look over loose solder joints, solder blobs shorting or something like this - this might correlate with your running "other" ecu...

Matt Cramer

We were closed July 4th, and I can't seem to find your email. I'm emailing back now, but I can't really answer this without a data log of the car as things are now.