Minor updates this week.

Some good and some, well.

.

.

business as usual.

.

.

I'm trying to keep it more frequent, to avoid having the multi-hour typing marathon when trying to catch up.

The PTSD is real!

Let's get the challenging bits out of the way first so we can end on a positive note: The Mk1.5, specifically the headlights.

.

.

I've spent some time chasing ghosts again and so far I've got nowhere really.

I did or observed the following:

* Pulled the cluster and some of the dash out, to check for loose or broken connections etc

- All looks ok, to my eye at least

* Cleaned the components

(fuses, relays and terminals) with contact cleaner, as they might have had an excess of grease in them

- No difference

* Replaced the above with known-working items

- No difference

* Tested the lights using just the flasher on the storks

- The relay clicks in he frunk but the mains don't come on.

Which is the same action as when I turn the headlight switch

* The side lights work as expected in all tests

I'm fairly sure the issue isn't in the cabin, it's in the frunk area.

I'm wondering if I've popped a fuse or relay in there that I'm not aware of?! However, in a bid to move forwards I'm now looking for a local auto electrician, which was Pete's suggestion.

I always forget that there are professionals out there who can fix these types of things, I don't need to do it all myself! Hopefully the next update will be after that process and we'll finally have some good news

It currently looking like this:



In readiness for the mapping session next month, I wanted to make sure everything ECU-related within my control was done.

The bit that had been nagging at me was whether or not the mapper would have the software to use and a data lead that could speak to the ECU.

He assured me it should be ok, but we all know I've had my share of obstacles with these cars.

.

.

To make sure I was covered I've sourced the Wolf EMS software, which was a bit of a pain but I did find, along with the legacy

.NET packages it required.

Once installed I tested it and everything ran as expected: a good start! The next step was sourcing a data lead to link a/my laptop to the v550.

It required a serial connection, which as we all know, if a bit retro now

After some research I found a serial to USB cable which was compatible with Windows 10/11 and is known to work with the Wolf ECUs.

I ordered it and this landed on our doorstep the next day:



Later that day I headed out and linked everything up for some tests.

Once I've assigned the relevant COM port to it in the software I turned the ignition and tried to connect.

This was what I saw:



followed by.

.

.



Win! So now I know the ECU works, the data lead works, I have the software working on a laptop, as well as a USB stick with the software and required

.NET packages on.

It might be OTT prep wise but I really REALLY didn't want to finally get my slot and have it wasted due to issues I could have prevented.

I'll be doing some more readiness checks on the car before it goes, as well as giving it a fresh tank of fuel on the day.
