News

60,000 kms with my Mahindra XUV700: 6th service & software updates

5th September 2024, 16:02 by Brij Gawde

I was hoping the OTA would bring the Google Maps projection to Instrument Cluster as well like the 3XO and the Roxx but that didn’t happen.

BHPian A.G. recently shared this with other enthusiasts.

6th Service of 60,000 Kms with other issues and highlights

Since the 50K service was done in 1st week of May and the 60K service in 1st week of August, there have been 02 unscheduled visits – one for steering calibration post tyre change and the other for getting a new Fastag. Despite the recent OTA update received for AdrenoX, the issue of Android Auto frequent disconnections (even when used with a USB cable) still persists. I was hoping the OTA would bring the Google Maps projection to the Instrument Cluster as well like the 3XO and the Roxx but that didn’t happen. Mahindra has yet to address the foot-ball in boot noise.

Due to a planned journey, got the 60K service done slightly early at 59,773 Kms even before the service reminder came up which had to be manually cleared on the drive later on. There was a huge rush that day due to the workshop being closed for almost a week due to Kanwar yatra but the service took no time as usual. What took time was the service action for updating the software for the driver-side power window motor which requires the inner door panel to be removed. Skipped the washing to save time and I was back on the road in just under 3 hours.

Reaching early even before 9 AM to get ahead of the queue

Saw the bays empty for the first time

Work in progress

Changed all 6 Engine Cover bushes as it was rattling (finally the bushes were available)

The Ultra V4 Oil (again no specs on the oil can) – this time 6L can be available

The naked door for the service action of software update

The total service bill came to Rs. 7,066/- which included 6L DEF, Oil Filter, Cabin filter, and V4 Ultra Engine oil with Engine cover bushes

Other issues:

During grueling summer heat the keyfob refused to work. Had hardly locked using the keyfob 30 minutes earlier. Thinking it might be the keyfob battery, unlocked manually which set off the alarm and despite starting with the keyfob in the backup position as indicated in the owner's manual, the alarm didn’t stop. Had a new spare battery in the glovebox and the replacement also didn’t help. Finally thought of disconnecting the battery of the XUV7OO only to realize the boot won’t open since the remote wasn’t working. Had to access the boot through the middle row after removing the entire luggage on the road and finally get the spanner. Once the reset was performed, it was as if nothing had happened. Tried again with the old keyfod battery and there was no issue and no pop-up of low battery on the cluster. Finally, after 15mins of sweating profusely (majorly because of embarrassment caused by the blaring alarm), learned the lesson to keep the spanner in the glovebox itself.

Since the 50K service, the wind noise has increased randomly and there has been no identification of the problem. It’s so random that I am afraid to discuss it at the workshop as I am not sure of the parameters to demonstrate the same.

The AdrenoX system seemed to have entered some archaic software version as the Fun with XUV7OO tile was not displayed and the Apple Carplay tile changed to ‘Coming soon

After returning from another trip, it felt that there was some wheel-bearing or similar sound coming from the rear which was completely speed-dependent. Demonstrated the same but I was surprised to find the blame being shifted on the tyres. The wear pattern was abnormal on 1 of the tyre which had a saw-tooth like tread on one of the edges. Googled the issue the term ‘Cupping’ came up which suggested shock absorbers as the primary cause along with worn-out bushes causing damage to tyre – obviously the same was not accepted and just the balancing with tyre rotation (already done at 60K Kms) was done again as a stop-gap arrangement. The noise, though is still there, has reduced probably due to the rotation of tyres.

At the workshop for diagnosis

While no uneven wear caused by the alignment is visible, the white triangular patch on the inside of the tread is lower than the darker triangular patch which is slightly raised which as per the workshop is causing the noise

Due to a sudden drop in ambient temperature, the tyre pressure also decreased the next morning. While all 4 tyres were at 29Psi, only one was throwing a low-pressure alert

Front Left showing low-pressure warning

Not related to Mahindra but the LED bulbs in the tail lamps started to flicker which I noticed on the 360 cam while reversing – replaced them with the original halogens.

OTA Update:

Upon turning ON the ignition to leave for home at night, for the first time got a notification for an OTA update. Since I didn’t have time for the update which usually takes 30 mins via USB at the workshop, I postponed the installation for the next day. After checking the in-built network had a strong signal, I started the process at 6:41 PM and immediately both the screens went blank only to be greeted by some notification 2 minutes later. The process took 20 minutes and everything came back to life at exactly 7:02 PM

OTA notification

Information after accepting the update

6:41 PM

6:43 PM

Update in progress

Before version

After version

Back to Back trips

Nainital – it turned out to be a nightmare even on a weekday during the June end and here is a screen grab of Google Maps. The actual time taken for this last 6.9 Kms was around 2.5 hrs

Ayodhya – a random discussion with family over breakfast culminated in an impromptu plan to visit Shri Ram Janmbhoomi Teerth temple. With the DEF level already around 41% and no time to spare, Mr. Prateek at Mighty Mahindra was kind enough to deliver 10L of DEF – called him in the evening and explained the situation and he promptly delivered it while returning back to his home. Small gestures go a long way.

At a rest area on the Lucknow Expressway – spotting a GS800 in the truck

Even the lampposts were unique

The final trip stats

Kashi – this trip was planned long ago and because of this, the service done slightly early. While going we went via Kanpur but on the return journey, we changed the plan once again and went to Ayodhya, this time for the evening aarti. The trip back to Delhi was mostly via Expressway and we were astonished with the FE with cruise set at 10 above the limit.

FE of 16.2 over 652 Kms (600 Kms on Expressway