EAS front bag changed now went to use my trusty FCR and no sign of life HELP!!!!

This site contains affiliate links for which LandyZone may be compensated if you make a purchase.

P38_Ireland

Well-Known Member
Posts
1,392
Location
Co Wexford, Ireland
right its 1 am and just changed my front drivers air spring as i noticed it was saging on one side by 40mm, so had a scap p38 lying up and knicked the spring from it and fitted it.

so started the engine left the door open for 15 mins to let the compressor fill and closed the door........ NOTHING......

so went and get my trusty FCR out and plug it in and guess what? the engine check light starts flashing and no sign of life in the FCR.... GRrrrrrrrrr

what to do???? im supposed to be setting off on a 400mile round trip at 6 am and need some suspension for the trip.

i know some of you will say try RSW software but bit of a snag. my OBDII cable finishes in a serial connection and my laptop is only 1 year old so doesent have a serial port. and cant find the USB converter anywhere

whay do these things happen atthe worst times?????
 
ok quick update i found the serial to usb converter pluged it in and same flashing on the dash with the engine check light. so i have unplugged the battery for 15 mins and waiting to try again.
 
Garrett

what did the FCR read?.... anything?

when I plug mine in and read the EAS ilways bleeps and all the lighs on the EAS button flash.. it did read a fault, I cleard and no probs now ,,,,

unless your OBDII plug is corroded and no power is getting to the FCR?
 
Last edited:
The eas communication is all routes through one pin on the obd plug, from memory I think it's pin 12. You need to make sure this is clean and that you also have 12v supply at the plug.
 
Ok so update is I got the rsw software working but still nothing from the fcr.

I have 2 OBDII leads and neither of them work with the fcr, how ever the rsw software works with the spurious lead the one I got from BBS doesn't seem to work. When I plug it in to either lead the fcr doesn't even light up. But only with the original cable make the engine check light flash 5 times in a row then nothing for a couple seconds then flashin again. Even with the BBS cable connected and no fcr this flashing occurs.

Ideas anyone?
 
If you can't contact the ECU with the FCR it is highly likely you won't be able to do it with the EASunlock either. Unless the FCR is duff that is. EASunlock works best with serial port and XP. I have not yet been able to get it to sync with a USB/serial adaptor on my ACER. But works perfectly every time on my steam driven Dell with serial port. However EASunlock is a far more useful tool for EAS work than FCR.
 
Ok so update is I got the rsw software working but still nothing from the fcr.

I have 2 OBDII leads and neither of them work with the fcr, how ever the rsw software works with the spurious lead the one I got from BBS doesn't seem to work. When I plug it in to either lead the fcr doesn't even light up. But only with the original cable make the engine check light flash 5 times in a row then nothing for a couple seconds then flashin again. Even with the BBS cable connected and no fcr this flashing occurs.

Ideas anyone?

The FCR and the RSW software require different obd leads and AFAIK are not interchangeable.The FCR requires +12V from the OBD socket.
I have both the RSW software and BBS MSV working on A Dell LT with Vista and USB with a serial convertor.
 
The FCR's P38 OBDII cable / interface is designed only to be used with the FCR and the FCR designed to be used only with its own cable / Interface.
You should not substitute any other cable and risk damaging something if you do.

As it has a 9 pin connector, It may look like other cables, but it actually has quite a sophisticated microprocessor based Vehicle communications interface built into the OBDII plug. This is accessed and commanded by the FCR using a custom command protocol that allows us to control it to route and convert data to and from the various custom communication channels and different OBDII pins, depending on what system is being accessed.

For example, when accessing the EAS system, the FCR issues a command to the microprocessor in the OBDII plug to switch to the Pins and data channelling designed specifically for the P38 EAS. It then issues a second command to get the microcontroller to wake up the EAS ECU and initialise comms with it, which it does totally independantly.

It might all sound a bit clever and overkill, but using a Microprocessor right at the OBDII plug, does provide the most reliable and dependable results on such an old and quirky system.

That is of course providing that the OBDII socket is not all Green and manky :doh:
 
Garratt,

Did you sort it mate?

no nothing yet

The FCR's P38 OBDII cable / interface is designed only to be used with the FCR and the FCR designed to be used only with its own cable / Interface.
You should not substitute any other cable and risk damaging something if you do.

As it has a 9 pin connector, It may look like other cables, but it actually has quite a sophisticated microprocessor based Vehicle communications interface built into the OBDII plug. This is accessed and commanded by the FCR using a custom command protocol that allows us to control it to route and convert data to and from the various custom communication channels and different OBDII pins, depending on what system is being accessed.

For example, when accessing the EAS system, the FCR issues a command to the microprocessor in the OBDII plug to switch to the Pins and data channelling designed specifically for the P38 EAS. It then issues a second command to get the microcontroller to wake up the EAS ECU and initialise comms with it, which it does totally independantly.

It might all sound a bit clever and overkill, but using a Microprocessor right at the OBDII plug, does provide the most reliable and dependable results on such an old and quirky system.

That is of course providing that the OBDII socket is not all Green and manky :doh:

hi BBS,

no the OBDII is fine. its clean and free of any dirt. strange thing is the EASunlock worked and reset the fault for me. any ideas what i should do? i have another P38 in the garden but the battery is flat will put a battery in it tomorrow and see if it even powers up on that

will update tomorrow.
 
ok plugged it in to both spare range rovers in the garden and there both lighting up the FCR but nothing from my car?? anyone any ideas whats up?

bare in mind the EASunlock works and the OBDII is clear of any dirt or debris and is fixed in place ie not come loose and hanging by the cables.
 
Don't forget that the FCR is locked to one specific VIN. You can't use it in two different motors, unless you've bought 2 licenses from BBS.
 
it seems not, i bought a new licence and connected it up to the new motor but then i couldnt get a read off the old motor so i have asked BBS guy if there is a way to have 2 cars on it at once im waiting for a reply .
 
Only if you buy 2 licences, thats why I am going MV with a limited number of modules to start with.

Think he has done. As far as i recall he bought it with a licence, used it on one of his Rangies then bought another licence and swopped it to his other. Surely with two licences he should be able to swop it from one to the other as he pleases. Or is that not the case and you cannot swap them about and you actually need two FCRs for two vehicles. And if he wants to swop it back he has to buy another licence?
 
Think he has done. As far as i recall he bought it with a licence, used it on one of his Rangies then bought another licence and swopped it to his other. Surely with two licences he should be able to swop it from one to the other as he pleases. Or is that not the case and you cannot swap them about and you actually need two FCRs for two vehicles. And if he wants to swop it back he has to buy another licence?


No the MSV can have 3 identities, so for example you could have 2 single vehicle licenses each locked to a different vehicle. I reckon if you have more than 1 P38 it's better to go for multi vehicle:D
 
Back
Top