New Pektron SCU coding

I was pointed towards this forum by some very friendly folks on Facebook and Kev at Remobilise so I'm hoping you can help.
I recently removed the Pektron SCU from my daughters 2006 TF and sent it down to Remobilise to get a faulty relay replaced and a second fob coded. Unfortunately Royal Mail have been as useless as normal and have lost the parcel!
If I acquire a new SCU, would I be able to use PScan to link this to the existing ECU?
Additionally, would I need two new fobs or would I be able to re-code the one I currently have from the 'lost' SCU? I assume PScan would also be able to link the new fobs?
Thanks.

I disagree about Royal Mail and have to say that.
Around here Royal Mail is the very best.

Evry would be my very last choice.

Im no Pscan expert but if it is a Pectron rather than a Lucas system it is my understanding that you should be able to do it but you will need the fob code before you start. I can’t remember how many numbers are in that code but think it is in the region of 20+.
The Lucas system is much easier.
im sure someone who can give you a definitive answer will be along shortly.

With PScan you can code Pektron SCU to your existing engine ECU.
However you cannot use existing fobs and code them to Pektron SCU because rolling code of existing fobs has gone so far that even if you would have 22 digit bar code of your existing fobs you would not be ablemto code them.
So you would need new fobs with 22 digit bar codes and you can code them to new SCU with PScan.

One thing to consider is when you are searcing for new Pektron SCU is to replace unreliable 5 Pektron relays with good ones before you put new Pektron SCU in your car. 

Roverlike wrote:

With PScan you can code Pektron SCU to your existing engine ECU.
However you cannot use existing fobs and code them to Pektron SCU because rolling code of existing fobs has gone so far that even if you would have 22 digit bar code of your existing fobs you would not be ablemto code them.
So you would need new fobs with 22 digit bar codes and you can code them to new SCU with PScan.

One thing to consider is when you are searcing for new Pektron SCU is to replace unreliable 5 Pektron relays with good ones before you put new Pektron SCU in your car. 

 

I can confirm that this is correct.  You can code new fobs but not ones that have been used before.  If the SCU is absolutely brand new it will not have any things like options and VIN number coded.  In theory I could make pscan do that, but I would need someone with a similar vehicle to read their config so that I could use that as a basis for a config for your car.  So if you want to do that you will need to talk to me.

I've recently been having a look at the eeprom contents on the Pektron SCUs and have a few pektron eeprom dumps, including one each for 120 auto, 135, and 160 respectively for 2005MY TFs (as well as dumps from earlier TFs, other MG Rover models, and a dump from a virgin pektron unit). I'm not sure the engine size makes any difference, but manual / auto and what options the car has fitted does. Happy to share these if it would help.

I'm not sure how the OBD communication with the pektron works, so pscan would be best placed to advise on this, but it should certainly be possible to write a suitable dump to the eeprom of another SCU after modifying the VIN number therein (not strictly necessary, but nice to keep things looking original imho).

The EMS (immobiliser) code would differ from what the engine ECU was expecting, so this would require a relearn, but I think pscan is already able to do this?

New fobs would be needed, but it would be worth keeping hold of the old ones too in case royal mail later find the original SCU, as the existing fob codes and rolling code window can be copied over from the old SCU (but only by re-programming the eeprom)

argentas wrote:

I've recently been having a look at the eeprom contents on the Pektron SCUs and have a few pektron eeprom dumps, including one each for 120 auto, 135, and 160 respectively for 2005MY TFs (as well as dumps from earlier TFs, other MG Rover models, and a dump from a virgin pektron unit). I'm not sure the engine size makes any difference, but manual / auto and what options the car has fitted does. Happy to share these if it would help.

I'm not sure how the OBD communication with the pektron works, so pscan would be best placed to advise on this, but it should certainly be possible to write a suitable dump to the eeprom of another SCU after modifying the VIN number therein (not strictly necessary, but nice to keep things looking original imho).

The EMS (immobiliser) code would differ from what the engine ECU was expecting, so this would require a relearn, but I think pscan is already able to do this?

New fobs would be needed, but it would be worth keeping hold of the old ones too in case royal mail later find the original SCU, as the existing fob codes and rolling code window can be copied over from the old SCU (but only by re-programming the eeprom)

I believe that I can read and write everything in the EPROM with pscan, except for fob data.  I'll be in touch.

Thanks everyone for the input.
I'm currently working with Kev at Remobilise who is sorting me a new SCU and fobs and I've reached out to PScan about buying the kit so hopefully it will be sorted shortly!

All kit is now acquired, but if anyone can help with the steps required within pscan to trigger the 'relearn' process in order to sync the EMS codes it would be hugely appreciated?

Once you've connected the replacement pektron SCU and reconnected the battery, you should be able to lock / unlock the car with the fob(s) and the body control features should be working again (horn, intermittent wipers etc), but you will not be able to start the car because the engine ECU will be expecting the EMS code from the original pektron unit.

Connect the pscan interface, turn on the ignition, and connect to the engine ECU (MEMS3). Then find this screen and click on 'Learn EMS code'. :

 

Unfortunately, I'm not able to guide you any more specifically than that as I haven't carried out this process with pscan, and can't check the exact process to reach this screen without connecting my pscan to the car, but it shouldn't be hard to find.