I'd like to think that any delay, especially if software related, has to do with how the use of the axle diff locks is tied in to each other and with the use of centre diff and low range.
Ineos seem to have designed in a series of single point failures with making various operations wholly reliant on software. Absolutely bizarre when you think back to all the statements about removing complexity, back to basics functionality and analogue simplicity.
The issues were illustrated with the Scottish reviews, both in the apparent confusion of some journos as to whether the axle locks were in or not and the HDC not being able to function until other systems/sensors confirmed diff locks were disengaged.
It seems to be a software house of cards in terms of the logic tree they have constructed.
The front diff will not lock with knowing the rear diff has been locked first, so, if you have a fault with the rear diff lock (or just the i/o signal to/from a sensor) then you also loose the use of a perfectly good front diff lock.
Loose the use of either the centre diff lock or the low range (or just the i/o signal to/from a sensor) and you then loose use of both axle diff locks.
It seems the complete opposite of building in redundancy in systems.
Yes there's the argument about why use a front locker before a rear or even before the centre diff but better to apply that as a driver input and retain the ability to override it if circumstances dictate it.
It all rather reminds me of the ASPW comments when taking out his ABS/wheel speed sensor and what a similar fault would do to a new Defender.
.
www.facebook.com
