Thread: Test for blocked exhaust - TD5

Originally Posted by schuy1

what makes you think it is blocked?

See point 1. I'm trying to figure out a simple way to test for blockages.

The turbo takes forever to spool up, so if there is back pressure, this may stop it from doing it quickly. Obviously, it is one of many possibilities, with a low probability. Fuel economy seems to be good, it isn't blowing black smoke, so not being over fueled.

Originally Posted by Alex 110

He's just poking fun at the diesels - poor guy, wedded to a V8 -we should pity him

Oh, The poor guy hasn't seen the light yet.... although driving a diesel isn't the same as a petrol v8, I don't miss the guzzling fuel economy, higher rego, higher maintenance, shorter drives between refills.

Now for a real insult - so he's just like a Landcruiser owner critizing a Land Rover.

Originally Posted by bsperka

Now for a real insult - so he's just like a Landcruiser owner critizing a Land Rover.

lol, i hope that isnt the best you can come up with.

Hi bsperka

To clarify what Offtrack says, if you plug the nanocom in and go to the instrument panel, you can record a log of the data that is displayed on the screen as you are driving. This can be captured on an SD card in a CSV format file which can be viewed in excel or other software package. It will really help diagnose the problem. Personally the log function and looking at the data has saved me a lot of time, frustration and $ in solving a couple of issues I've had, supported by the valuable advice of the members of this forum.

To capture the data, you first need to have an SD card inserted into the Nanocom. Then plug the nancom in, power it up and go to the instrument screen. At the bottom of the instrument read out screen towards the right side is a blue disk icon. Tap that and it goes to a file screen. Type in a file name hit ok and ok again and logging starts. Go for a drive and when finished tap the same icon again to stop logging and the nanocom will give an alert that the logging has stopped. Power the nanocom off, remove the SD card, plug it into your computer and open the file in excel, to look at the recorded data. If you can't make head nor tail of it, post the file here and the experts will be able give some comments.

There is a bit of a learning curve with the nanocom, but once you have used it a few times it all becomes easy.

Cheers

Steve

Originally Posted by bsperka

Mate, for a start what is a record? But seriously, this is the first time that I've seen that stated on AULRO. I'll see if we can do that, after removing some other potential causes. This is the first time that I've used the nanocom to fault find, rather than clear faults, so I'm on a learning curve.

Still a lot of new records released even in 2013: New Releases - Vinyl , but I digress.

It's often discussed in the electronic diagnostics forum which is where you'll find several years worth of posts about using tools like the Nanocom.

Let me google that for you

Most of the Td5 troubleshooting information is in that forum, so unless you been looking you wouldn't have seen it.

I'd add to Steve's post that you can save information from any screen on the nanocom that has a disc icon. In settings screens you'll get a file with the settings of the module. This is handy for backing up injector codes, or BCU settings for example.

In any section of a module that displays realtime data clicking save will create a file which logs all of the data available, not just what is displayed on screen. When you are recording inputs you need to touch the disc icon a second time to finish the data capture. I've found this has to be done before turning the engine off, otherwise the Nanocom looses communication with the ECU and the data doesn't save.

There are a number of ways of visualising data. If you use the Td5 engine module to record the fuelling you can view the data with Graphic Viewer CSV which you can download here:
td5 map suite

I've been using a free app on OSX which I find a bit more versatile, but you can also import into Excel.

http://www.aulro.com/afvb/electronic...ation-osx.html

Bottom line is that it's a very powerful way to examine the way engine systems are behaving.

cheers
Paul

Originally Posted by OffTrack

Broken record here but I'll say it again: "record fuelling inputs to file while doing a test drive and post up the CSV file."

The ability to record inputs is the main feature that makes the Nanocom better for diagnostics than the Hawkeye. You should use it.

OK, I'm being a PITA, but after your post yesterday, I looked through the diagnostics section today (all 17 pages), as well as doing a search using your username, as well as searches using the terms "fuelling inputs" and "fuel". I struggled to find anywhere that you have said it... there are some places where it can be inferred though. Just saying.

That being said, it's a good diagnostic approach that may assist in resolving some engine related problems. It would be worthwhile putting up a post that talks about this approach in some detail.

Originally Posted by bsperka

OK, I'm being a PITA, but after your post yesterday, I looked through the diagnostics section today (all 17 pages), as well as doing a search using your username, as well as searches using the terms "fuelling inputs" and "fuel". I struggled to find anywhere that you have said it... there are some places where it can be inferred though. Just saying.

That being said, it's a good diagnostic approach that may assist in resolving some engine related problems. It would be worthwhile putting up a post that talks about this approach in some detail.

My comment about broken record was in reference to the other thread jadan had started.

I suggested to jadan, who you are helping out, that recording fuelling inputs might be helpful:

http://www.aulro.com/afvb/discovery-...rd#post1858754

And I also suggested it in reply to a post you made in the same thread yesterday:

http://www.aulro.com/afvb/1865107-post29.html

Maybe you should spend some time reading the documentation that came with the Nanocom instead of trying to annoy me.

I'm not trying to annoy you about this, but obviously I have. Sorry about that chief. And yes, I'm trying to help jadan, but this thread is somewhat incidental to that at this time, hence its not against that thread. As one of the possibilities, I was wondering if a blocked exhaust could make the engine behave like this. This lead me to wondering how to detect a clogged / blocked exhaust in a diesel. Googled how to detect this in a diesel. Not much help there, so I thought I would ask the forum how they do it.

So, the topic is about trying to detect a blocked exhaust. If grabbing how the engine is behaving will assist in detecting a blocked exhaust (or other engine issues), then I'm interested in finding out more / how. Hence the request on how to do this and use them in general. Someone pointed out that the postings where under engine diagnosis, so I checked there, before putting up the previous post.