stewd
Active Member
If that's the only reason, does anyone have a wiring diagram for the ODB socket on the P38. As have quiet a few blank ODB plugs laying around.
stewd
Active Member
True, but wouldn't I need to buy multiple unlock codes when wanting to use it on a p38 followed by a L322?
Nanocom is not available on the L322...
You buy the unit and unlock it for a particular P38 type (GEMS, Motronic or Bosch) and you can then use it on any P38 of that type....
If you then want to use it on a different Variant i.e. you bought a GEMS version, and wanted to use it on a Bosch Diesel - the unlock is about £50 and you can then use it on both any GEMS P38 or any Bosch P38....
The Faultmate can be setup as a Multiple Vehicle System which will cover all versions....
Not sure on the Hawkeye, that maybe VIN Locked.
On the L322 the RSW All Comms isn't VIN Locked.
stewd
Active Member
Ok, now that's been explained it makes a bit more sense.
I was looking at the hawkeye before but I prefer the computer interface and not just a hand held device.
Will have a look into the nanocom though,
As well as a play with a couple of blank ODB plugs, as at the end of the day it's all 1's & 0's, shouldn't be to hard to communicate to the ecu.
I was looking at the hawkeye before but I prefer the computer interface and not just a hand held device.
Will have a look into the nanocom though,
As well as a play with a couple of blank ODB plugs, as at the end of the day it's all 1's & 0's, shouldn't be to hard to communicate to the ecu.
stewd
Active Member
Best of luck. A lot have tried and failed.
Ummm... I'll see how long it takes until I get bored of the idea...
StuckAgainSteve
Well-Known Member
There are 10 kinds of people in the world - those who understand binary and those who do not.
...Well, somebody had to say it!
tnseal
Active Member
OK for you I have looked at the early model.
Pin 1 is Air suspension delay timer off timer wire colour SR
Pin 2 N/A
Pin 3 N/A
Pin 4 Ground wire colour B
Pin 5 Ground " " BP
Pin 6
Pin 7 BECM Module (data bus) + HEVAC Module (heating) + ABS (Brakes)+ ECM Engine diesel has two wires and petrol uses only Pin7 +( Most probably with Ground I guess)
All pins to Pin10 N/A
Pin 11 Air Suspension ECU Wire colour WLG
Pin 12 Air Suspension " " " WK
Pin 13 Air Bag Diagnostic Module YK
Pin 14 " " " " YG
Pin 15 BECM Module + same as 7.
Pin 16 Engine compartment Fuse number 33 5a wire colour N
Wire colours.
B= Black
G=Green
K=Pink
L= Light
N=Brown
O=Orange
P=Purple
R=Red
S=Grey
U=Blue
W=White
Y=Yellow.
I have taken this from a cd and it is at your risk.
The wiring seems to be different from nanocom to nanocom unit and they use two leads to connect. On the web, there is a guy with the pin outs. it was on my old pc, before some child sent me a worm. I think I'll cut the phone cables next Summer.
Pin 1 is Air suspension delay timer off timer wire colour SR
Pin 2 N/A
Pin 3 N/A
Pin 4 Ground wire colour B
Pin 5 Ground " " BP
Pin 6
Pin 7 BECM Module (data bus) + HEVAC Module (heating) + ABS (Brakes)+ ECM Engine diesel has two wires and petrol uses only Pin7 +( Most probably with Ground I guess)
All pins to Pin10 N/A
Pin 11 Air Suspension ECU Wire colour WLG
Pin 12 Air Suspension " " " WK
Pin 13 Air Bag Diagnostic Module YK
Pin 14 " " " " YG
Pin 15 BECM Module + same as 7.
Pin 16 Engine compartment Fuse number 33 5a wire colour N
Wire colours.
B= Black
G=Green
K=Pink
L= Light
N=Brown
O=Orange
P=Purple
R=Red
S=Grey
U=Blue
W=White
Y=Yellow.
I have taken this from a cd and it is at your risk.
The wiring seems to be different from nanocom to nanocom unit and they use two leads to connect. On the web, there is a guy with the pin outs. it was on my old pc, before some child sent me a worm. I think I'll cut the phone cables next Summer.
Last edited:
stewd
Active Member
And a-lot of people right now are trying to work out the maths!
Not bored yet, Just trying to source a complete ECU unit for a p38 along with Sensor's etc.. So can lay it out on the bench instead of testing it on mine and blowing things up...
Do remember there is more than one ECU and they are all linked in some way to the BeCM...
The trick will be to get the right protocol in order to get the ECU's to enter diagnostic mode and talk with a host/client software, and for the returned message to be correctly interperated as a fault.
LR used different protocols for the different system, and also different leads may be required with different cross overs to ensure compatability.
The Engine ECU's I believe talk on the OBD (EOBD) standard as they had to by law in 1996, but the diesel (Bosch) system is totaly unique to Bosch as Diesel ECUs didn't need to unitl 2004 or something...so again another one to look into.
Once you have a working network of vehicle ECUs that the BeCM will acknowledge and recognise, plus the myriad of sensors to attach thereto and a way of simulating their correct (and incorrect) working parameters and be able to interigate the ECUs to ensure they are indeed working as required...then simulating different fault scenarios whilst logging the ECUs response to such...then you'll be onto a good start !!
Do remember there is more than one ECU and they are all linked in some way to the BeCM...
The trick will be to get the right protocol in order to get the ECU's to enter diagnostic mode and talk with a host/client software, and for the returned message to be correctly interperated as a fault.
LR used different protocols for the different system, and also different leads may be required with different cross overs to ensure compatability.
The Engine ECU's I believe talk on the OBD (EOBD) standard as they had to by law in 1996, but the diesel (Bosch) system is totaly unique to Bosch as Diesel ECUs didn't need to unitl 2004 or something...so again another one to look into.
Once you have a working network of vehicle ECUs that the BeCM will acknowledge and recognise, plus the myriad of sensors to attach thereto and a way of simulating their correct (and incorrect) working parameters and be able to interigate the ECUs to ensure they are indeed working as required...then simulating different fault scenarios whilst logging the ECUs response to such...then you'll be onto a good start !!
And it will possibly be 2050 by then. And i don't mean ten to nine.
Good luck,many have tried and failed.The chap who sells the Allcomms,has basically given up trying to crack the P38 protocols.try emailing him and chat to see the difficulties he encountered.His website is http://www.rswsolutions.com/:D
tomcat59alan
Well-Known Member
A translation is available for anyone that needs itDo remember there is more than one ECU and they are all linked in some way to the BeCM...
The trick will be to get the right protocol in order to get the ECU's to enter diagnostic mode and talk with a host/client software, and for the returned message to be correctly interperated as a fault.
LR used different protocols for the different system, and also different leads may be required with different cross overs to ensure compatability.
The Engine ECU's I believe talk on the OBD (EOBD) standard as they had to by law in 1996, but the diesel (Bosch) system is totaly unique to Bosch as Diesel ECUs didn't need to unitl 2004 or something...so again another one to look into.
Once you have a working network of vehicle ECUs that the BeCM will acknowledge and recognise, plus the myriad of sensors to attach thereto and a way of simulating their correct (and incorrect) working parameters and be able to interigate the ECUs to ensure they are indeed working as required...then simulating different fault scenarios whilst logging the ECUs response to such...then you'll be onto a good start !!
kurtjohnson10
Well-Known Member
You took the words out my mouthDo remember there is more than one ECU and they are all linked in some way to the BeCM...
The trick will be to get the right protocol in order to get the ECU's to enter diagnostic mode and talk with a host/client software, and for the returned message to be correctly interperated as a fault.
LR used different protocols for the different system, and also different leads may be required with different cross overs to ensure compatability.
The Engine ECU's I believe talk on the OBD (EOBD) standard as they had to by law in 1996, but the diesel (Bosch) system is totaly unique to Bosch as Diesel ECUs didn't need to unitl 2004 or something...so again another one to look into.
Once you have a working network of vehicle ECUs that the BeCM will acknowledge and recognise, plus the myriad of sensors to attach thereto and a way of simulating their correct (and incorrect) working parameters and be able to interigate the ECUs to ensure they are indeed working as required...then simulating different fault scenarios whilst logging the ECUs response to such...then you'll be onto a good start !!
