(Solved)2001 GU Patrol (Y61) going into limp home mode

Below post starts with car model 2001 GU Patrol (Y61) symptom that car kept going into limp home mode, then recommended to have one Foxwell AutoMaster Pro NT624 scanner to solved. How this story goes? Go on reading following parts. Hope it helps.

Car model: 2001 GU Patrol (Y61) with a 4.8 lt petrol

Symptoms:

My car kept going into limp home mode and i could not drive it (well).

Scan Tool to use:

Foxwell AutoMaster Pro Series tools: Foxwell AutoMaster Pro NT624

I use AutoMaster Pro NT624 to check ECU and read out fault code as below:

PO134 H02S1 (B1) – Heated O2 Sensor Bank 1 Sensor 1

P1122 ETC FUNCTION/CRC – Throttle Body Actuation -Electronic Traction Control

P1123 ETC Mot RLY/CRC – Electronic Traction Control – Motor Relay

After cleared the fault code, I got the left code:

P1122 ETC FUNCTION/CRC – Throttle Body Actuation -Electronic Traction Control

Then I have a quick check of the live data for the Throttle Body motor, when graphed against the Throttle Position Sensor, revealed that the throttle body motor was in-fact intermittently faulty. Causing a correlation error -Throttle position sensor not accurately reflecting the a accelerator position sensor.

Then I decided to do a quick check on the fault code:

PO134 H02S1 (B1) – Heated O2 Sensor Bank 1 Sensor 1

As this would take a drive cycle (potentially) to reset. We naviaged to the live data for the both O2 Sensors and graphed them together. With O2 Sensors, the general rule of thumb is to see them switch between rich and lean (0.1 -ish- and 0.9 -ish- Volts) around 8 times over 10 seconds at 2000 rpm. Watching each O2 sensor signal I counted the crosses (switching between 0.1 – 0.9) and found that wile the bank 2 (rear) sensor was crossing around 5 times (a lazy sensor) the bank 1 (front) was struggling to make 3 crosses. Both sensors where more often on the lean side. So although not technically a current fault, I was suggested to also replace my O2 sensors as they are both currently lazy -one more so than the other- and likely to need replacement in the future.
source:http://www.foxwellsupport.com/2001-gu-patrol-y61-going-into-limp-home-mode-solved/

(Solved)2001 GU Patrol (Y61) going into limp home mode

Below post starts with car model 2001 GU Patrol (Y61) symptom that car kept going into limp home mode, then recommended to have one Foxwell AutoMaster Pro NT624 scanner to solved. How this story goes? Go on reading following parts. Hope it helps.

Car model: 2001 GU Patrol (Y61) with a 4.8 lt petrol

Symptoms:

My car kept going into limp home mode and i could not drive it (well).

Scan Tool to use:

Foxwell AutoMaster Pro Series tools: Foxwell AutoMaster Pro NT624

I use AutoMaster Pro NT624 to check ECU and read out fault code as below:

PO134 H02S1 (B1) – Heated O2 Sensor Bank 1 Sensor 1

P1122 ETC FUNCTION/CRC – Throttle Body Actuation -Electronic Traction Control

P1123 ETC Mot RLY/CRC – Electronic Traction Control – Motor Relay

After cleared the fault code, I got the left code:

P1122 ETC FUNCTION/CRC – Throttle Body Actuation -Electronic Traction Control

Then I have a quick check of the live data for the Throttle Body motor, when graphed against the Throttle Position Sensor, revealed that the throttle body motor was in-fact intermittently faulty. Causing a correlation error -Throttle position sensor not accurately reflecting the a accelerator position sensor.

Then I decided to do a quick check on the fault code:

PO134 H02S1 (B1) – Heated O2 Sensor Bank 1 Sensor 1

As this would take a drive cycle (potentially) to reset. We naviaged to the live data for the both O2 Sensors and graphed them together. With O2 Sensors, the general rule of thumb is to see them switch between rich and lean (0.1 -ish- and 0.9 -ish- Volts) around 8 times over 10 seconds at 2000 rpm. Watching each O2 sensor signal I counted the crosses (switching between 0.1 – 0.9) and found that wile the bank 2 (rear) sensor was crossing around 5 times (a lazy sensor) the bank 1 (front) was struggling to make 3 crosses. Both sensors where more often on the lean side. So although not technically a current fault, I was suggested to also replace my O2 sensors as they are both currently lazy -one more so than the other- and likely to need replacement in the future.
source:http://www.foxwellsupport.com/2001-gu-patrol-y61-going-into-limp-home-mode-solved/

Original Xentry Connect C5 remove hard disk

It's aimed to help remove the hard disk from the original Xentry Connect C5 (SD connect C5) Star diagnostic tool.

you need:

Benz SD C5 Connect

a tweezers
a screwdriver

Here goes the key- remove the hard disk within STAR C5 step by step.

remove the  protective layer

use the screwdriver to to take off the screws

  

take off the cover and the card

 

turn to the other side and take off the screws and the cover

  

this is the Xentry connect hard disk

you cannot remove it now

turn to the other side

use the tweezers to take off the side cover gently (pay attention to cables connected)

  

back to the side with the hard disk

now, you can remove it

remove the hard disk from sd connect c5 - SUCCESS!

Done!

http://blog.mbstarshop.com/2016/07/19/xentry-connect-c5-remove-hard-disk/ 

Diagnosing and coding BMW E31 E38 using Foxwell NT510 scanner

I found this Foxwell NT510 scanner chart that shows the specific function per BMW model which is helpful. foxwellshop has NT510 scanner for $179, but I found it on ECS for $199. Seems pretty reasonable for all the readout capability and the coding it claims. Plus you can buy additional software (only $70USD) for one of other manufacturers (Including AU FORD, BMW, Chrysler, Fiat, GM, Honda, Hyundai, Holden, Land Rover, OPEL, Toyota and VAG) as well. One another thing to consider about this tool is that the software updates for it are free for the first 18 months only, and after that only the cost of updates is only 60USD.

I have to use for my BMW E31 and E38. I can speak to ease of use and functionality.

As you can see below chart is Foxwell NT510 Scanner workable function on BMW E31.

Here I list some I tested for your reference.

BMW E31 especially early are going to be very limited on features. This isn't due to the tools or software used, it's just the DMEs don't have the echo commands to provide all the detailed data.

Electronic parking brake reset, SRS reset, and service intervals are the "big 3" packages that our tool has.

As for coding injectors after replacement with Foxwell NT510, it's an accessible option in the menu list... I haven't tried it because my injectors are fine but there's a long list of menus in fuel injection you can mess with. Injector replacement and adaptations were in there and you could access it.

Foxwell NT510 can read out manufacturer specific codes. Most handheld tuners that will also pull codes only pull the basic P codes, not your BMW specific code lines. Now don't get me wrong P codes are very useful, they'll send you down the right path (most of the time), but manufacturer specific codes are going to tell you what door to open.

Foxwell unit is a standalone tool, no need for a laptop, this can be a positive or negative depending on the style tool you like to use. If you're use to a GUI interface on a laptop going to a scan tool style interface will take some getting use to.

Going by a quick look once Foxwell releases the coding update the tools look to have very similar functions. Also no VIN lock on the foxwelll scan tool, use it on as many cars as you'd like.

In conclusion:

Foxwellshop extended us an evaluation copy of this unit and I was really impressed with it. The various functions remind me of the vaunted VAG-COM system we've used in Volkswagen & Audi for years. Such a simple and affordable scanner is really a plus for this platform.

http://www.foxwellsupport.com/diagnosing-and-coding-bmw-e31-e38-using-foxwell-nt510-scanner/

Coding BMW E70 using Foxwell NT510 scan and coding tool (Feedback)

I just received one Foxwell NT510 scan and coding tool today, I am working my way through this scan tool and so far I have been relatively impressed.

Played around on my BMW E70 for a bit, covers ABS, Airbag, Electronic Parking Brake, some EWS/CAS, Active Suspension, Service Resets for $179.

ON my E70 I have use Foxwell NT510 codes all sorts of convenience features for things like door locks, windows, tailgate and lighting.

Moreover, OBDII for more than just BMW protocol along with BMW specialized/proprietary codes and Bi-directional control for many modules and systems in the vehicle for testing and troubleshooting purposes. Everything from rolling windows up and down, turning lights on and off and controlling the HVAC/IHKA. Also Live data from many of the subsystems in the vehicle, so switch inputs can be monitored and on newer vehicles with a true TPMS with individual wheel sensors you can see the tire pressure.

Foxwell NT510 can be updated to include AU FORD, BMW, Chrysler, Fiat, GM, Honda, Hyundai, Holden, Land Rover, OPEL, Toyota and VAG for approximately $70 for one brand. These updates are manufacturer specific.

http://www.foxwelltool.com/wholesale/software-authorization-for-nt510-multi-system-scanner.html

With a tool like the Foxwell NT510 Scanner for BMW, all you need to do is keep and interface in the car and you will always have at least an OBDII tool at hand when out on the road.

So for around $179 USD, the Foxwell tool looks very promising. There is always newer update that is supposed to offer more coding capability as well. Unclear what coding capabilities will be released, not sure if it is more personalization of modules and lighting changes or something more in depth.
http://blog.foxwelltool.com/foxwell-professional-scanner/foxwell-nt510-scan-coding-tool-code-bmw/