ArntyR

Hmm...fobs + scu back to Technozen then, I reckon

Hi Mario5. I'm not an expert but I'm replying because feel your pain.

I assume you're working with new fobs + batteries c/w a new 22 digit (?) authorization code? (Btw do the new fobs need a sticker 'pulling off' to make them work work? I say this because I bought an inspection light recently and found this was why I couldn't get it to work...)

If not it sounds like your immobiliser isn't responding to your fob (since I think the injectors aren't being actuated as part of the process) and this may well be due to the 'curse' of the Pektron scu or more specifically a duff relay (or pair) in the scu. IMO your 2004 TF is well overdue* if those scu relays haven't been checked out, let alone upgraded. I doubt that the scu would need 'replacing' but if you chose to, I think you'd have to program a brand new pair of fobs for the next scu (since I gather used fobs can't be synched with Pektron; only brand new)

In any case, If I was in your position I think googling 'Technozen' would be my first port of call. Sorry I can't be of more help but I bet he'll sort you out very quickly.

*If it's any consolation my 2010 TF's relays were Technozened in Jan '20 and I thought that was 'pushing it'...

Please keep us posted.

Yes, curious...especially the fact that EKA doesn't get a mention in the SAIC user manual, yet the Pektron scu gives it up to Pscan interrogation.

I'm getting the feeling that we'll never solve the mystery of the missing SAIC EKA. Other than markvrs no other PScan/SAIC owners have engaged in the thread to confirm or deny their own EKA, I'm afraid

Erm, sorry I meant unplug it from the scu (if that's the same as the 'bcu' on yours and Mark's pics) or is your bcu the ecu?  

(Isn't it the Pektron scu that allocates EKA?)

Brill...thanks...and is my test method okay?
(or will there be wisps of smoke?)

wow...thank you both, PScan and markvrs... 

I've included a pic of my SAIC Pektron input plugs. There's 4 m/plugs which tallies with markvrs pic

Sooo...I use the markvrs diag to find which m/plug has that colour combination of wires (2 lilacs and a brown), remove it and use + probe on each one of those pins in the m/plug (the darker lilac and the brown) one at a time, - probe to an earth, and see if twisting the driver door key/switch changes the voltage? (are the wire colours actually the same as on the  diagram?) 

 

Okay, assuming the voltages change, we'll have affirmation that the door switch is registering and that the EKA number signal gets to the scu...

Arrgh...what if they don't change - and (aargh) what to do next if they do change?

PScan your live data for the first three columns - 'Door key switch / Drivers sill down / Drivers sill up' - seem to support mine , so I reckon my switches should be working ok (thanks...)

Question is, if your MGR ecu, scu and switches support EKA on your Rover 25 why wouldn't the MGR ecu, scu and switches support it on my SAIC? Could there be anything else 'EKA dependent' that we might have missed out, I wonder?

Back to post #196373 I mirrored with my SAIC TF (non-working EKA) what you did with your Rover 25 (working EKA), pscan, on an MGR NNN100743 ecu (remapped) / 1541 scu combination and managed to download the attached live log file (I think - never done this stuff before...)

I haven't enough experience to analyse it, but mine's very different later on than yours.

I wonder, then, if the secret to my non-EKA SAIC action lies with a SAIC door micro-switch that isn't able to function the same way as the MGR setup?

The ecu/scu combination works with MGR TFs, after all... Got any thoughts on this?

Best wishes 

ps I recall my unlock process mirrors yours, except that I haven't done the extra-hard twist. I accepted that it'd stay down + I'd have to lift it physically.

That's welcome info technozen and it gives me hope to keep trying despite no mention of EKA in the SAIC owner guide.

But nobody else has reported that they've got it to work for them. I'd have thought someone (else) would respond. 'markvrs' has been a like-minded contributor and he can't get EKA working on his SAIC, either. He originally drew my attention to the lack of mention of EKA in the SAIC owner manual and suggested that denaturing it might be a consequence of further security update to Thatcham1, along with the separate battery-powered, isolated, alarm/screech function.

And thanks for your input pscan. I can't see a direct link with my results yet but if I try to replicate your process and get the same results, again, it'll keep me motivated to keep chipping away at the problem. (I haven't done a log file yet so this'll be a new experience...) If you wouldn't mind duplicating my process, too, it'd give me something to compare with and if your results are the same as mine - but your EKA works - it'll prove that I'm barking up the wrong tree.

I'm still suspicious about why my own doorlock investigation seemed to show that there seemed to be a constant a 'controlling default'...