Rovertech.net
http://www.rovertech.net/forum/

Update 041C
http://www.rovertech.net/forum/viewtopic.php?f=144&t=152301
Page 1 of 1

Author:  pscan.eu [ Mon Feb 26, 2018 11:35 pm ]
Post subject:  Update 041C

This update contains the following features:-

EMS2000 (KV6) only in ISO mode:-
Information now displays the VIN number
Erase codes now performed in the same way as a T4 rather than Snapon Modis
Feature to learn EMS code from 5AS or Pektron

LE500 / TF135 instrument panel:-
Reset service indicator

The previous version 041B details are here

Author:  JCooper924 [ Mon Mar 05, 2018 9:15 pm ]
Post subject:  Re: Update 041C

Hi Phillip.
I own a 05 MG TF . When I bought it , it didn't come with the EKA . :cry: It has two fobs but one of them is not very reliable . If the car isn't used for a while the fob needs it's battery removing and refitting to make it work again . The fitting of new a new battery makes no difference. I was wondering if the latest update has still got fob syncing/programming as being unsafe ? If I end up buying a s/h fob does it have to have the barcode for it to be successful ? I don't use the car in winter so I can wait for this pesky fob issue to be sorted .
Thanks for all your continued hard work .

Regards John

Author:  pscan.eu [ Mon Mar 05, 2018 10:42 pm ]
Post subject:  Re: Update 041C

Technozen seems to have done quite a lot of testing, if you have read his posts then you know as much as me.
We have not had any feedback from any other customers, either good nor bad.
I would say that reading the EKA is very low risk. if you have a Pektron car then definitely update pscan and read your EKA code and note it down.
If you loose or break your last fob but have the EKA then you can code in new fob(s), but if you don't have the EKA then you are going to have to pull out the Pektron and send it to Technozen.

For a Pektron car you can only program in a brand new key fob and it must have the barcode.
If you buy a used fob even if it comes with a bar code the "rolling code" may have rolled forward too many times and then it will not work because the car and the fob will be too far out of sync. My understanding is that the "rolling code" moves on every time that you press a button.

You can buy an Avon fob from Technozen, or you can buy a genuine one from XPart.

The difference is cost, and that the genuine one disables the automatic timeout of the immobiliser if the fob is inside the car. With Avon ones if you unlock the car but then don't turn on the ignition for ages then you will have to press unlock again before you can actually start the car.

Author:  Thierry KZN [ Wed Mar 07, 2018 10:39 am ]
Post subject:  Re: Update 041C

greetings from a sunny South Africa ...
Just some feedback:

I have tested the 041C update on a 2003 TF and all seems to work well ....
The Pektron unit displayed the EKA code and I made note of that :)

Tested all the actuators and all responded as expected (no rear wiper and headlight wipers of course)
Tested the heated rear screen -- starter did not respond :D .... I don't have a heated rear screen either.....

Philip ... thank you for an absolutely brilliant diagnostic tool ....
It is an invaluable tool to have, especially when I am based in SA as there are very few MG "experts" available, if any.

BEST investment I made ...... :thumbup: :thumbup: :thumbup:

keep up the great development work ---- it is appreciated big time

Author:  JCooper924 [ Wed Mar 07, 2018 9:59 pm ]
Post subject:  Re: Update 041C

Hi Phillip. ECU Identifier NNN100743
Today I installed the update and tried it on my 05 TF . The EKA was indeed displayed but I tried numerous times to use it following the instructions and was unable to override the immobiliser / start the engine . However I did successfully test the various relays which work apart from the HRW and the screen washers which didn't respond . Both these do work but not through the interface . With regards the EKA and after returning from where the car is garaged , I had a look at the wording of how to input the code from the owners manual and I think I may have spotted the problem . The manual says that the ignition should be off which it was and that the first movement of the key in the lock should be to unlock . The manual doesn't mention holding the key to the lock position for 5 seconds . I know most folks out there are going to say it must be me whos a numpty but, I was in the motor industry for 45 years . I am going to try again tomorrow and after that I think that I will have to remove the BCU and with the fobs send them to Technozen for him to sort although I will speak to him before I do .
This is still a great piece of kit so please don't let me give you the impression of having a moan as that is not the case , just the quirkiness of owning an MG/Rover .

Regards John

Author:  pscan.eu [ Thu Mar 08, 2018 12:12 am ]
Post subject:  Re: Update 041C

John, this is what I posted in the Pektron section. It would be good to validate that it's correct if you can :-


I tried out the EKA on the 2003 ZR with Pektron and from memory this is what I did:-

1. Lock the car so that the alarm is on, alarm LED on etc.
Remove the fob from your key ring and put somewhere out of radio range of the car; you want to prove that you can do this with just the key.
2. Put the key in the drivers door lock.
3. Turn the key to "lock" and hold it in "lock" for five seconds. This will cause the alarm to go off but just ignore it.
4. Enter the first digit of the EKA by turning the key to "unlock" that number of times.
So if the EKA is 4321 you turn the key from the centre to unlock and back to centre, 4 times.
5. Enter the second digit of the EKA by turning the key to "lock" that number of times.
So if the EKA is 4321 you turn the key from the centre to lock and back to centre, 3 times.
6. Enter the third digit of the EKA by turning the key to "unlock" that number of times.
So if the EKA is 4321 you turn the key from the centre to unlock and back to centre, 2 times.
5. Enter the fourth digit of the EKA by turning the key to "lock" that number of times.
So if the EKA is 4321 you turn the key from the centre to lock and back to centre, once.
6. The alarm LED now goes out.
7. Wait five minutes, but not more than ten minutes.
8. Unlock the lock, open door and start engine.

Author:  JCooper924 [ Thu Mar 08, 2018 12:46 pm ]
Post subject:  Re: Update 041C

Hi Phillip.
I will verify it but it wont be today as we have had another dumping of snow here so it could be the weekend before this happens . Sorry for being a pain ! :mrcool:

Regards John.

Author:  JCooper924 [ Thu Mar 08, 2018 5:14 pm ]
Post subject:  Re: Update 041C

Hi again Phillip.
This afternoon I coupled the pscan to my TF and can verify that I have followed the instructions to the letter but the car will not accept the EKA that is being read . While operating the key in the lock ( starting with it in the lock position to activate the alarm) I find that as I get to input the 3 rd number which in this case is 9 the alarm tries to lock the door as I am in the process . The alarm LED doesn't stop flashing and the alarm continues to activate as I input the last digit . All the other parts of this update to this point are working as in live data, I can even see the good fob showing that it is working on the screen of the lap top. Activating the relays via pscan is as I said previously , working apart from the HRW and the screen wash .
As you have said , I think it would be unwise of me to try and perform a sync/reprog of the fobs until I have a reliable EKA . I am beginning to wonder if there is a problem with the micro switches on the drivers door lock rather than the EKA being wrong . I think that my only course of action now is for me to admit defeat and remove the Pektron unit and send it away for repair with the fobs .

Regards John

Author:  pscan.eu [ Thu Mar 08, 2018 8:52 pm ]
Post subject:  Re: Update 041C

I developed the Pektron code by borrowing Rob Bell's ZR and trying lots of things out. He didn't seem too bothered if I bricked the car which was useful.

I definitely tested that I could enter the EKA, and that the diagnostic protocol still worked with just the EKA. Therefore this seemed a good safeguard to advise customers to use.

Unfortunately I don't have access to a TF, and so it is a bit harder to test, develop, validate or advise. I suppose that if you are willing to pull the Pektron and send it off to Technozen then you don't need to be too fearful of messing with it. The worst that can happen is that you disable the car, and have to send it off anyway, so no great loss.

I found an old post of Technozen which might enable you to test the key barrel switch inputs.

Quote:
Taken from the original SCU Technical Training course documentation....

SCU Self-Test Mode

Self Test Mode can be entered manually as follows;

* With the driver's door shut, depress the door sill button.
* Turn the ignition on, off and then back on again.
* Lift the driver's door sill button.

This sequence of events must be completed within approximately 5 seconds. On successful entry the horn will sound briefly as confirmation and the vehicle will become immobilised.
Once the self-test mode has been entered, normal functionality of the SCU is suspended and certain alarm related inputs can be tested. A transition on any of the switch inputs will cause the security LED to flash briefly to acknowledge the input.
The following inputs can be tested by manual operation in this fashion.
* Sill up
* Sill down
* Passenger / Rear doors open
* Drivers door open
* Bonnet open
* Boot open
* Key barrel switches
* Inertia switch
Failure to access the self-test mode indicates a problem with the sill up, sill down or ignition switch inputs.
A spare key will be required to test the key barrel switch inputs, as one will already be required to turn the ignition on.

Author:  JCooper924 [ Thu Mar 08, 2018 9:39 pm ]
Post subject:  Re: Update 041C

Hi Phillip .
Thank you for your reply . I have been in touch with Technozen and spoke to him regarding this annoying problem . He confirmed my suspicion that my TF is not receiving a valid EKA signal from the door lock switch. To explain according to him there are 3 switches in the locking system and if I recall correctly , one sends an unlock voltage to the BCU , one sends a lock voltage to the BCU and the third is to indicate that the lock is in the vertical position . These switches ( which are not serviceable ) must give a clear signal to the pektron unit as to which position it is being turned . If one switch is lazy or the wiring to it is corroded the pektron will not respond to the EKA sequence that is trying to be sent. This is possibly the reason that when trying to input the EKA, the pektron unit says what's going on and sends a lock signal to secure the system as the key is being turned to the unlock direction in the sequence . To sum up , my TF has two possible faults , one with the fob that I was aware of and a wiring or latch switch fault . As the car is on sorn and parked away from my house and access to tools it will be a while before I am able to fully diagnose the exact cause with EKA.
In no way should you think that your fantastic bit of kit is not doing its job and I hope that I haven't given you that impression as that was not my intention .

Regards John

PS I will get back to you with my findings .

Author:  pscan.eu [ Thu Mar 08, 2018 10:10 pm ]
Post subject:  Re: Update 041C

Don't worry, I didn't get that impression.

Author:  JCooper924 [ Mon Mar 12, 2018 2:11 pm ]
Post subject:  Re: Update 041C

Hi Phillip .
I am no nearer to sorting this problem with my TF as I bought another central locking latch and fitted it yesterday . The BCU is still trying to override my input of the EKA halfway through the process by locking the door . I think the only answer is to give Technozen a call and arrange for me to send him both fobs and the Pektron unit and let him work his magic . I believe that this bizarre problem can only be sorted by having him code a new fob and see if there is anything weird with the BCU .
Thanks again .
Regards John

Author:  JCooper924 [ Mon Apr 16, 2018 5:29 pm ]
Post subject:  Re: Update 041C

Hi Phillip.

I just thought I would let you know how I was progressing with my TF and it's troublesome Pektron . You may recall me telling you about my efforts to use the Pscan to sort out one of my key fobs. Unfortunately I was unable to get the car to accept the EKA code that the Pscan had given me so I could progress to the next stage . I honestly thought it was me that was doing something wrong trying to get the EKA to release the immobiliser. After talking to the brilliant Paul Brown ( Technozen ) , I removed the SCU and let him work his magic. After getting it back I have found that the car now accepts the EKA and Pscan has now let me rewrite the code to a more favourable one . I have to say that Paul provides a really good service and I would recommend him to anyone with a similar SCU fault.
Thanks once again for your help in sorting this out .
Regards John

Author:  MrEcosse [ Sun Apr 29, 2018 12:10 pm ]
Post subject:  Re: Update 041C

Just to say thanks for this update. Happy to have now reset the service indicator on LE500 #350

Author:  pscan.eu [ Sun Apr 29, 2018 1:10 pm ]
Post subject:  Re: Update 041C

First confirmation that it works 8)
Thanks!

Page 1 of 1 All times are UTC [ DST ]
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
http://www.phpbb.com/