Does VCDS support the new Amarok Mk2?

[AdvTechTS]

Title says it all, Does VCDS support the new Amarok Mk2?
What is the best interface for these vehicles (HEX+CAN or HEX-NET)?
Cheers, Chad.

 

[Dr Sheldon]

Plug it in, try it and be the first ??

 

[Uwe]

Don't know for sure, but seriously doubt it, since the new "Amarok" is actually Ford Ranger dressed in VW clothing.

Spoiler

That's only fair, since the new BEV Ford Explorer is a VW ID.x dressed in Ford clothes.

-Uwe-

 

[Mats@MFT]

... interesting to see if the VW in Ford clothing will work???

 

[Eric]

I expect it will, with the next beta (23.5). Feedback welcome.

 

[AINils]

@Eric is it possible to get a hand on that beta 23.5 as we have a customer who can try it at a Ford Amarok ;-)

 

[Mats@MFT]

Already news on 23.5 vs. Ford Amarok?

 

[Eric]

Yes, as expected it doesn't work well.

 

[webasto]

tried my hex-v2 on a delivery 2023 4cyl petrol and virtually no functionality just reads the vin and "some" module hardware numbers.

 

[Bruce]

tried my hex-v2 on a delivery 2023 4cyl petrol and virtually no functionality just reads the vin and "some" module hardware numbers.

Please post an autoscan so we can see what the tool is seeing. Don't know how? See the blue bar at the top of the page - the How To menu.

 

[AINils]

Is there any news in 23.11 about Amarok MK2?

 

[Eric]

No, this is all Mercedes comms and addresses, and we don't feel it's the right move at this time to go into another adventure of implementing a model from a non-VAG manufacturer that doesn't exist in the US market for us to test on.

 

[NEtech]

No, this is all Mercedes comms and addresses

You probably mean Ford

 

[Eric]

Yes I'm still reeling from the Crafter experiment

 

[AINils]

Understood, will communicate this to our customer

 

[MNZ]

Yes I'm still reeling from the Crafter experiment

Does this mean you are unlikely to support at any stage?

We have a lot of Amarok's in our daily workflow and have already started servicing these but have no way of doing a service light currently. We may have to turn them away if there is no support.

 

[Uwe]

Does this mean you are unlikely to support at any stage?

Never say never, but I would indeed say it's unlikely.

We learned something of a lesson with the old Crafter, being a mix of VAG and MBZ modules, and it, just like the Amarok, was never available on this side of the pond. A model not being available here usually isn't a big problem with a vehicle is all VAG, but when you throw in some other manufacturer's modules, it becomes a nightmare.

-Uwe-

 

[MNZ]

Never say never, but I would indeed say it's unlikely.

We learned something of a lesson with the old Crafter, being a mix of VAG and MBZ modules, and it, just like the Amarok, was never available on this side of the pond. A model not being available here usually isn't a big problem with a vehicle is all VAG, but when you throw in some other manufacturer's modules, it becomes a nightmare.

-Uwe-

Ok Thanks for the reply. It might be good anyway as working on Ford is not really what we want to be doing.... haha

 

[golfi_vend]

Had similar question few days ago. Using ODIS, odis can read some data, but basic coding or adaption is not available. Also Odis tries to map some of its modules to logic VAG numbers. Like body module to D0009 and headligh range to D0055.

Also had a chat with dealer and any issue with this Ford Amarok will result replacing a module. And a cherry on top, if You mess PDI and adapting keys You must replace some modules and order new keys. As who ever has worked with Ford Immo will know.

May have to pull ForScann out to test.

 

[Sebastian]

May have to pull ForScann out to test.

I was thinking FCOM, but generally same idea. Try a Ford specific product...