Hi all. Sorry I am late to the conversation.
I'm afraid I am not associated with PSI motorsport at all.
I do know how these magic boxes work and i must admit, I am not a fan of them.
Cheers.
Simon

That's definitely a D2 software version.
Perhaps the case got a bit grotty and they swapped it out?

Please do investigate with the nanocom. That'll give us the definitive answer on what it is as this has certainly piqued my attention.
I wasn't going to say anything about the installation, which is why I kept it to the word "Interesting". It's polite.
I am in Pembrokeshire.
Dropped you a message about the P38 thor immo. Didn't want to go full on advertising it here with prices as I don't know if it's breaking any rules.
Let us know what the nanocom reveals please.
Thanks.
Simon

Actually.
Looking at this again a little more closely, I think I know what's going on in there.
The scorching to the around the capacitor PCB is in the injector driver area with the 30382 injector driver I.C. taking some damage.
This is I pretty much guaranteed how the ECU has failed.
Now, onto the ECU itself.
That does like a later P38 ECU due to the fact there is a capacitor omitted from the board up by the power connector. This was done by Bosch when they revised some of the power components.
The mods done by the I/O interface and processor I.C.s looks like some kind of immobiliser bypass. I know the signals are definitely in that area. So I may not have been the first to work out how to do the Thor immobiliser bypass then. All I can say is mine is much neater and only 3 wires.
The 14 pin IDC connector may well have been used for setting up / data scanning and possibly to change the rev counter pulses back to 4 cylinder.
I can see a power feed coming from the black capacitor marked CVF to it which makes me wonder if there's anything underneath the connector.
So all in..
I think you do have a P38 engine ecu in your D2 that's been modded to work with it by persons unknown.
As I said, I can get the P38 one you have actually running. Tackling the rev counter, I have not looked at as never needed to. I can do it. just not looked at it.
Cheers.
Si
Cheers.
SImon

Wow! That's some interesting mods going on in there! Would be nice to know who did that and what they were trying to achieve.

Ok I appreciate you are now looking for a D2 ecu. I am sorry I don't have one in stock. For some reason prices shot up on them mid last year to the point I could not justify having one sitting on the shelf.
However for now, I can bypass / remove the immobiliser from the P38 THOR one for you so you can at least still use the car if you like.
The only thing will be the fact the rev counter will be showng double the actual RPM.
If I can be of assistance in that way, drop me a message.
Cheers.
SImon

OK the 0261204901 is the P38 THOR engine ecu.
The D2 V8 has a few different part numbers. 0261204476, 0261204895 come to mind. I can't remember the US Spec 4.6 number.
There is a possibility that some one has either changed or reprogrammed the flash in the ECU for a discovery one. They are electronically pretty much identical, or they may have simply changed the casing on the ecu.
What I would do is talk to it with a nanocom and see what the ecu tells me regarding part numbers etc, however you may came up against some issues using the P38 one as stated above.
Cheers.
Simon

Brian, a couple of caveats for your information.
The P38 engine ECU is not the same as the Disco 2 V8 one.
It differs in 2 ways.
1: The immobiliser signal used in the D2 is completely different to the P38.
2: The tachometer (rev countr) output signal is different as well. The P38 outputs 4 pulses per crank revolution (8 cylinder output). The D2 one outputs 2 pulses per revolution (4 cylinder output).
So if you have bought a P38 engine ECU for your D2, I'm afraid it won't run unless you have it de-immobilised.
So I do hope you have bought a D2 engine ecu for your D2. If so it's a case of pop it in, do a security learn and away you go.
Cheers.
Simon

Harv,
I had no idea what the Mobi-lize was or existed until you mentioned it. Looking at the information I can glean off the web (I think that the product is discontinued) , it looks like the emulators I used to fit to the GEMS ecus.
On the nanocom, the Security Mobilize bit with a YES means the ECU has either received a correct security code from the BECM or the immobiliser has been switched off.
So basically it means the ECU is in a ready to start / run the engine condition.
If it is NO, the engine will not start.
So on your motor, I'd expect to see it in the YES condition as it's received the correct code from the BECM.

Harv wrote:

I checked mine with Nano, and it was already set. Do you think this is as good as the Mobi-lize?

davew wrote:

Good work/deduction Simon, Cheers !

Dave,
it was you that fired up the creativity, so thank you.

Hi all.
Following on from the conversation with DaveW on Bolt's thread about my Thor emulators I have been looking into this infamous F-Out box for the GEMS engine ECU.
I must admit, I didn't find a lot of information aside from the technical bulletin out there, but I thought I'd have a bash at replicating one.
I am pleased to say that after a few false starts I have successfully been able to reproduce said item so now the GEMS ECU no longer requires an emulator if running standalone or with a problematic BECM.
Demonstration of the outcome on my youtube channel, which I have linked to below.

https://www.youtube.com/watch?v=YsoaaFrEzM0

Hope this may be of help to some.
Cheers.
Si

Martyuk wrote:
I do think the possibility of running the Motronic ECU as standalone is great, as it opens up the possibility of using the engine/ECU in standalone environments which previously was only confined to the using the GEMS version... I'm a big fan of the Rover V8 and the thought of being able to use it in other projects - but with the later engine management systems is quite food for thought....

Morning Marty.
Thanks for the input and yep. 100% correct. Up until I got to work on the P38 THOR I had never seen a security system where the engine ECU was hard coded and the security module has to be programmed to match the engine ECU. I had always worked with ECUs that you match to the security so to me it was a bit like the tail wagging the dog, but there we are and there it is. Been a fun project if a little frustrating at times.
The exact reason why this was developed was for a standalone solution for competition. I must admit I envisaged it being used in engine swaps / kit cars etc but not in the P38. It was only after talking to a P38 specialist and a few others on my social media that I have ended up here via Bolt.

Dave, that's very interesting. I must admit I was unaware of that document and the procedure.
I can make this "F-Out" box using one of my emulators very easily. Infact it would take literally minutes to do with the way the code is set up.
Next time I have a GEMS in, I'll have a play with this.
Every day is a school day. 😀
Edit This seem to be for the USA spec GEMS, which I have never had a look at, so may / may not work on the UK spec.

The immobiliser code in the GEMS is not universal. If it was you could just swap them out one for another and it'd be a plug and play part provided it was going on another P38. As it is, you have to sync the 2 up using a tool with dealership levels of coding (nanocom testbook etc), but then you know all this I am sure.
They have different codes ranging from 0000 to FFFF and all numbers in between. The immobiliser code is actually programmed in the BECM and programmed from the factory.
RE: The K-Line protocols, that's a nightmare in itself. I did do a bit of work in the TD5 protocols a few years ago for a small project which worked reasonably well, but since that, I have done nothing really on that side and let's face it, for the price of one of BBS's offerings compared to some units out there, they are pretty competitive price wise.
Can Bus is a different matter. Done a fair bit on the Can side of things with the BMW work I do.

Ah that does indeed look like the GEMS solution I actually do as well. Granted the security code will be different as there's 65000 or so of them and the board is a different shape but they will be similar. Maybe I should get one and scope the output just to see what security code they do use.
On the subject of the protocols they are obfuscated and some are encrypted as well, however all are very robust protocols which are thoroughly error checked.
It's just sadly LR always seem to drop one single clanger (BECM) in what could have been a brilliantly reliable system.

Dave,
In all honesty, it's completely different solution to the Synchmate.
That's basically a box of tricks that re-synchronises the BECM to the engine ECU immobiliser code in the event the BECM throws a sulk.
The way mine does it is by sending the immobiliser code from the emulator board fitted inside the engine ECU, thereby removing the need for the BECM all together. There is a small wiring mod needed to remove the starter motor crank request from the BECM as well to make it truly standalone, but that is simply a case of joining 2 wires together so the ignition key on position 3 (engine start) is then fed directly to the starter motor relay and the engine turns over irrespective of the BECM status.
It's also worthwhile mentioning that all my emulators have the relevant immobiliser code for that unit programmed in non volitile flash so it cannot forget the code like the BECM has a tendency to do.
I am not familiar with the OZ chip device, however I have heard about it. I am sure that was for the GEMS ecu and possibly very similar to the way I do the GEMS ecu myself. The THOR however is a completely different encryption to the GEMS, so whilst the emulator is the same hardware (I standardised it right across the range), the software in the microcontroller (programmable chip on the board) is completely different between the GEMS, P38 THOR, DSE and D2 THOR.

Good morning all.
Firstly, donmacn, if I can help out, drop me a message when you are ready.
Now, on with the introduction.
I am the Simon mentioned above and yes the immobiliser on the P38 THOR, GEMS and DSE can be bypassed by emulation.
By emulation I mean I have designed a small (22mm x 22mm)electronic board that can be fitted inside the ECU and connected via 3 wires that will send the correct encrypted code to the ECU so the ECU is happy and will run without the need for interaction with the BECM.
The project mentioned by Bolt above was actually done for an off road competition vehicle that the owner wanted to fit a P38 4.6 Thor engine into, so I was thrown the challenge to make it standalone.
I already had the D2 Thor and GEMS ECU standalone solution in place so we could have gone down that route using a D2 ECU from the USA Spec 4.6 D2 or swapping over to a GEMS unit, but neither of those were ideal, so I looked into the P38 THOR ECU to see how it ticked.
A lot of people say the D2 Thor and the P38 THOR ECUS are identical. They are not. There's a lot of changes in software and some in hardware between the 2 and even across different revisions of the same ECU there are differences.
This little project took over 12 months to crack with the difficult bit being finding the first crack in the armour. After that first in road on the encryption, it took a week to get a finished solution out for initial testing, which went well and is still out there competing to this day..
After unveiling the project to the public on social media with a bench test video demonstrating the ECU being happy, I was immediately messaged by 3 people saying "That's impossible! It can't be done!" Errr... Ok... I guess I have done the impossible then 🤣🤣.
Well I guess the proof of the pudding is in the eating and I now have ECUS in the USA , Europe and Malaysia all working standalone on my humble little boards.
It was only when I was talking to one of the P38 specialists here in the U.K. that I realised that the BECM can be somewhat of an Achilles heel on the P38 that can leave you stranded for numerous reasons and I daresay you know a lot more than I do on that subject. Well this little board (and a wiring mod for the starter motor engage request) will mean the BECM is not involved with the running of the engine at all so irrespective of the BECM status, you'll always get the car to start and drive, which may give some a bit of peace of mind.

Other projects I have done are the L322 BMW 2926cc Diesel and the L322 BMW 4.4 petrol ECU both standalone as well as the TD5.

Any questions as all about what I can do, please post here or drop me a message and I'll be happy to explain further.
You can also see the P38 and others being demonstrated on my youtube thingy.
https://www.youtube.com/channel/UCwKSHm0fu3k5WX5whp0H6MA

Cheers.
Simon