Many Thanks for all your recent comments and honest feedback.
Just like a P38 Range Rover, over an L405 Range Rover, the Nanocom is not the latest and greatest technology.
It is certainly not some multi core 1,X Ghz processor powered multi touch smart phone / tablet, just like the P38 is also not some collection of Super fast,
networked ECU's.
Few will likely know and appreciate that technologically and diagnostically the P38 is a collection of different ECU's from many different manufacturers that all
impliment communications that are specifically designed to be as evasive, incompatible and as non standard as possible. EG, Try finding 1387 on a Baud rate table or imagine inverted or differeing voltages over any standard. Their design aim is entirely to prevent any third party access from easily communicating with them.
Some are so akward and odd that they cant even share the same pins on the Diagnostic connector, hence there are 3 pairs plus a special wake up pin for the EAS.
The ABS, needs to be reset manually by recycling the Ignition after ever communication session to put it to sleep, so you can have another session with it or
with any of the other ECU's it shares the same pins with,
Of course this is all written in the documents that it seems so few take the time and trouble to read and the Nanocom gets so quickly and easily blamed for so many of the communication issues that are actually P38 ECU diagnostic communication design issues.
Of course the Nanocom is not perfect and does share at least some blame, because to do what it does, the Nanocom uses no less than three seperate microcontrollers, a main one, one for the screen and touch inputs and one for the Vehicle Comminications.
These try their best to stay in sync, but sadly their syncronisation can all to easily get overwhelmed and the entire system crashed by users imagining it to be
some super responsive smart phone and over enthusistic button pressing, function switching input expectations that it simply cannot keep up with. Also a single
glitch in Communications can reek havok with it.
I am very glad to read that at least some have figured a good part of this this out and appreciate our efforts to add the P38 to the Nanocoms coverage capabilities..
With a good clean diagnostic connection, a little understanding and effort in reading the provided documentation explaining about the various vehicles various ECU foibles, a little patience and appreciation,I still believe the Nanocom is about as good as it gets for accessing a P38 IMHO, FWIW.
Warmest Regadrs
Colin
.