Android OBD2 reader, error code P1335

[pugslyyy]

Using a bluetooth OBD2 adapter and the android "Torque" program I am able to read fault codes with no issue - but the live data is completely wrong (engine RPM, coolant temperature, etc). Anyone else try messing around with this?

Also - related question - Fault Code P1335, any experience with what causes that on a Fuso?

Thanks!

 

[digitaldelay]

I'm guessing "Piston Position Sensor 1", if there is such a thing on a Fuso.

Jason

 

[pugslyyy]

I'm guessing "Piston Position Sensor 1", if there is such a thing on a Fuso.

Jason

Yes that's what I found when I used the power of the internet.

Was hoping for a little more enlightenment but thanks for the response.

 

[digitaldelay]

Yeah, my Fuso knowledge is pretty limited (zero) but boy, can I Google, haha!
Jason

 

[SkiFreak]

Unfortunately, I have come to the conclusion that the only scan tool that can read Fuso ECUs correctly is the MUT-III.

Over the past two years I have purchased one and tried three different scan tools, all of which "appear" to read the raw data coming out of the ECU but they all deliver incorrect readings. Like Pugsly, I have used different software (including the Torque application) with very similar results. Looks like it works but all of the data displayed is wrong.
A basic test is to try and retrieve the VIN. If the tool cannot do this then it is unlikely that it will read any of the other engine information correctly either.

The cheapest MUT-III readers I have found have been around $600-$700 from China. These appear to be clones of the genuine Mitsubishi MUT-III readers. Ultimately I will probably get one of these Chinese clones, but paying out that much money without having a guarantee that it will work has been the stumbling block to date.
It should be noted that the MUT-III reader's software also interprets the error codes for you and tells you, in plain English, what the issue is.

If anyone has had success in using any other type of scanner to read Fuso ECU data, please share, as I have not been so lucky.

 

[pugslyyy]

Unfortunately, I have come to the conclusion that the only scan tool that can read Fuso ECUs correctly is the MUT-III.

Over the past two years I have purchased one and tried three different scan tools, all of which "appear" to read the raw data coming out of the ECU but they all deliver incorrect readings. Like Pugsly, I have used different software (including the Torque application) with very similar results. Looks like it works but all of the data displayed is wrong.
A basic test is to try and retrieve the VIN. If the tool cannot do this then it is unlikely that it will read any of the other engine information correctly either.

The cheapest MUT-III readers I have found have been around $600-$700 from China. These appear to be clones of the genuine Mitsubishi MUT-III readers. Ultimately I will probably get one of these Chinese clones, but paying out that much money without having a guarantee that it will work has been the stumbling block to date.
It should be noted that the MUT-III reader's software also interprets the error codes for you and tells you, in plain English, what the issue is.

If anyone has had success in using any other type of scanner to read Fuso ECU data, please share, as I have not been so lucky.

Ah something like this then? http://www.ebay.com/itm/New-Mitsubi...subishi-MUTIII-MUT3-car-scanner-/111148515330

 

[SkiFreak]

Yep... that's the one.
Be aware that the scanner in the listing you link to does not include the flash card. This is used to reprogram the ECU. If you just want to read the data coming out of the ECU then this may not be an issue for you.
If you do end up buying one of these MUT-III scanners, please let me know how well it works.

 

[pugslyyy]

Yep... that's the one.
Be aware that the scanner in the listing you link to does not include the flash card. This is used to reprogram the ECU. If you just want to read the data coming out of the ECU then this may not be an issue for you.
If you do end up buying one of these MUT-III scanners, please let me know how well it works.

I will -though at the moment I don't have $600 sitting around burning a hole in my pocket!

 

[SkiFreak]

I don't have $600 sitting around burning a hole in my pocket!

Unfortunately, I can easily relate to that comment...

 

[gait]

I'm about two days into having to get serious about OBD whatever. My Canter is 2005 and doesn't really have an OBD2 socket (it has one wire) which I believe I can remedy.

Enough excuses though. There are things called PIDs (Parameter Ids). There's the number they have inside the ECUs, and the label they have in the software. In Torque, like most other live data viewing programmes, there seems to be a way of defining "custom PIDs". Its a trial and error process. The numbers in the ECUs seem to be two digit hex. The labels in the software seem to be of form Pnnnn.

Its done that way because originally there was only one ECU, now there's an "ECU for everything" and the OBD connection communicates through CAN Bus to all of them.

Not easy to get right though. There are also calculations from raw data to display.

There's odds and sods about the ECU numbers in various places. There'll also be the effect of any translation MUT has done.

Wouldn't mind guessing there's a monster configuration file for Torque and other software that has the cross-references by vehicle.

P1335 is EGR related for some makes. Somehow need to look at the PID (or at least the equivalent translation for the error code) to the two digit number for the engine ECU - its in my engine service manual but Owen tells me its not in his.

Not much help sorry, I'm still trying to figure out why my ECU reported the engine running backwards. Though in looking at this problem I've read that 45 means the two engine speed sensors are a bit out of phase, which sounds much better than engine running backwards.

 

[SkiFreak]

Being able to run the engine backwards might be a useful feature if you lose reverse gear...

I have no idea how you are figuring all of this out, but I am definitely interested in reading about your attempts to do so.

 

[gait]

at the moment you are getting the raw thoughts as I step my way through it all. I'll hopefully receive a cable in Lhasa, make it work, then I'll write up the concise methodical "how to" - assuming it works of course, I'll know in 2-3 weeks.

Quick example is "mode". The bits in the PC/Android software about "error" or "data" or "actuator" is reflected in the standards and ECUs as "mode".

As for how. I once had the illustrious title of "solutions architect". There are only so many ways these sorts of systems can be architected. But the research is iterative - comparison of what Mitsubishi have done to the standards and look at the software. Just a plod with a lot of experience!

 

[pugslyyy]

at the moment you are getting the raw thoughts as I step my way through it all. I'll hopefully receive a cable in Lhasa, make it work, then I'll write up the concise methodical "how to" - assuming it works of course, I'll know in 2-3 weeks.

Quick example is "mode". The bits in the PC/Android software about "error" or "data" or "actuator" is reflected in the standards and ECUs as "mode".

As for how. I once had the illustrious title of "solutions architect". There are only so many ways these sorts of systems can be architected. But the research is iterative - comparison of what Mitsubishi have done to the standards and look at the software. Just a plod with a lot of experience!

Even though the engine monitoring info I get from Torque is suspect, I'm pretty confident that the error codes I'm getting are accurate. I had an engine overspeed condition (downshifting) and it read and identified the code correctly.

The P1335 code is a hard fault - it comes back every time I clear it, but doesn't illuminate any dash lights.