Foxwell NT510 on 2015 Rapide S

[jevansio]

Hi I've bought a Foxwell 510 Elite (with Aston Martin plugin) my Rapide and I'm struggling to get any more info than comes from a bog standard scanner

It won't read either of the bank 1 or 2 ECUs. It won't read any sort of ABS ECU. Is this due to me having the Bosch ECU?

I'm trying to find out if a DSC error is due to a wheel speed sensor falling out, is this possible on the Foxwell?

I also don't seem to be able to see the plethora of service reset/control items the blurb reckons it can do on an Aston

I'm on the verge of just returning it unless anyone can enlighten me on what I may be doing wrong to make this unit more usable than my £10 Bluetooth scanner

Ta

Jay

[jevansio]

So I returned the Foxwell. Saw on a video review of the xtool d7(s) it showed Bosch ECU and 8 speed transmission as modules so took a punt and ordered one. Sadly my Rapide is in getting these issues fixed at garage but I plugged the d7s into our MK3 TT and easily got a screen showing the live wheel speed sensors. It looks massively capable and I will report back if it indeed can talk to all systems on the Rapide 8spd

J

[Bluebottle_GB]

I'll be interested in your results please - I too have a 2015 Rapide S and I had an odd "High engine temp" warning come on the other day after not many minutes of gentle driving. Sat at in a petrol station car park for 30 minutes waiting for the AA man; even turning on the ignition the fans went crazy and the message came up. Then we turned it on to allow him to run diagnostics and it cleared itself... I would like to see if I can narrow down which engine temp sensor is possibly on its way out by reading the codes (he didn't do the diag in the end as the fault had cleared).

[jevansio]

I haven't forgotten.... car is still in garage :/

[jevansio]

Ok so I got the car back today and obviously hooked the xtool straight up.

First up the Bosch and 8spd buttons in the Aston Martin specific section do not work.

But 3 ECU show up in the general OBD section which identify themselves as Bosch 1 and 2 and 8spd.

I can get live wheel speed data from the abs ecu. I can also get live MAF data from the Bosch ECUs

So although it's a shame the Aston Martin specific buttons don't work I do believe it's capable of getting more data than the Foxwell 510

If there is anything specific you want me to look for I can

Also the passenger odb port has absolutely bot all on it any any more

J

[Swissdriver]

As my Vanquish is also equipped with Bosch ECUs, could you please check if xtool supports misfire monitoring? It would be very helpful to read out the live number of misfires during a drive.

[jevansio]

That was something I was specifically interested in too. I need to have a good look tomorrow. There are multiple misfire mention including being able to look at each cylinder. There is also some overriding Misfire Test which shows as passed. But this is all sat on the drive. I need to take it out and see if the counts get a couple of numbers in there as mine all show 0. I will report back

One thing I can't find is the ability to either trigger or read the status of the exhaust bypass valves

[jevansio]

Been out today and those 12 cylinder misfire counts all show 0. That surely can't be right even on a perfect car? Here's some screenshots

Edited by jevansio on Saturday 9th May 21:28

[Swissdriver]

Thanks for testing it out! Honestly, I’m not sure if zero misfires is realistic. Can you click on the 'Misfire Cylinder Data' tiles? There should probably be a few misfires during a cold start, perhaps they are only visible during live monitoring?

[yvr]

I'm using a "Launch X431 Pro Elite" with my 2016 Vanquish. It looks similar to the xtool D7S in pictures, and is also an android tablet like the xtool. The X431 seems to have good support for Aston.

I get a similar result when monitoring misfires -- no misfire counts reported (on a 35K km car). On my tool I think it's labelled something like "damaging misfires", and I do recall reading somewhere that there are two categories of misfires on these cars (maybe a Bamford Rose video?).

Like you, I get nothing useful from the "body" ODB2 port.

[Simpo Two]

yvr said:

I get a similar result when monitoring misfires -- no misfire counts reported (on a 35K km car). On my tool I think it's labelled something like "damaging misfires", and I do recall reading somewhere that there are two categories of misfires on these cars (maybe a Bamford Rose video?).

Like you, I get nothing useful from the "body" ODB2 port.

If my experience of a DB9 is anything to go by, there are two types of misfire, 'A' and 'B'.

I'd say zero misfires is impossible so that suggests it's not registering. Which reminds me of the 'misfire recording activation technique'... Is it a button? Nope. Is it in a menu? Nope. It's five suicidal run-downs from 70-20mph without touching anything. You couldn't make it up - but somebody did!

Hopefully after a certain year they changed it.

[Swissdriver]

Simpo Two said:

Hopefully after a certain year they changed it.

They did change it for the Bosch ECU models, but it actually got more complicated. For example, step 20 of the official service bulletin states: "Keep the vehicle in third gear and accelerate up to 4,000 rpm, then decelerate to 1,500 rpm ten times."

I suspect we only see MOT-relevant misfires because that is all the standard OBD interface is required to provide. Unfortunately, the true misfire count is hidden. Currently, apparently no aftermarket OBD tool can access the deeper data as shown in AMDS.

[jevansio]

I will try the 4000 to 1500 coast technique and report back. I recall Aston 1936 needed to do similar to get the misfire data on his DB9

Going back generally to the capabilities of the xtool I'm really happy with it. I'm trying to track down the source error of the dsc service required intermittent warning and it's showing me the live wheel speeds seem fine but that the lateral acceleration reported to one of the ECUs keeps dropping out

[jevansio]

@Swissdriver The first screenshot was what was behind the misfire tiles.

[Simpo Two]

Swissdriver said:

They did change it for the Bosch ECU models, but it actually got more complicated. For example, step 20 of the official service bulletin states: "Keep the vehicle in third gear and accelerate up to 4,000 rpm, then decelerate to 1,500 rpm ten times."

'...whilst holding a kipper on your head'. Madness. Why is the function not active by default?

Swissdriver said:

I suspect we only see MOT-relevant misfires because that is all the standard OBD interface is required to provide. Unfortunately, the true misfire count is hidden. Currently, apparently no aftermarket OBD tool can access the deeper data as shown in AMDS.

It may be worth visiting somewhere with AMDS just for peace of mind.

[Swissdriver]

@Simpo Two: The misfire monitor should be enabled by default, and jevansio’s screenshots confirm it is active. Newer Astons are also less prone to losing misfire correction data than older models.

@jevansio: There are a few more steps required to complete the engine misfire corrections. I am happy to email you the full procedure.

[Emilio Largo]

Swissdriver said:

Currently, apparently no aftermarket OBD tool can access the deeper data as shown in AMDS.

I assumed (one of) the main aspect(s) of buying the recommended ThinkDiag diagnostic tool(s) for the Bosch-managed engines was the ability to show misfire data in detail. Would be disappointing, if not.

[AM-DB9]

jevansio said:

Been out today and those 12 cylinder misfire counts all show 0. That surely can't be right even on a perfect car? Here's some screenshots

You sure you're on the EMS OBD2 port and not the Body port?

[jevansio]

Definitely bud. Only 1 port has any life on my car. The other hasn't shown a sign of life on 3 different scanners now

[AM-DB9]

Here is a setting on my scan tool - 155 Misfire Monitor Enabled