u/Longjumping_Ad_2301

So I’m trying to read my Motronic 4.3 ECU with MotronicSuite.

I’m able to connect to the ECU, and MotronicSuite appears to communicate with it normally. However, when I use Read Flash Content, it downloads a 64 KB BIN file but the contents are usually all 00, so no actual ECU data is being read.

At one point, using another PC, I managed to save three BIN files, but all three had inconsistent results:

• volvo.bin: 64 KB. All 65,536 bytes are 00. Empty / failed read.
• volvo2.bin: 64 KB. Contains data only at the beginning; from approximately 0x0D75 onward, everything is 00. Very incomplete read.
• volvo3.bin: 64 KB. Contains a lot of real data, but the last ~8 KB are 00. Partially successful read.

Does anyone have any ideas what could be causing this?

As far as I can tell, I’m following all the required steps and have the correct drivers installed. I’ve also experimented with the COM port settings in Windows, including the FTDI latency timer, but the results are still inconsistent.

At this point I’m starting to suspect a hardware issue with the KKL cable itself.

Extra info:

• Volvo 850 T5, 1996
• Bosch Motronic 4.3
• Cheap Chinese KKL 409.1 cable with pin selector switches
• Using pin 3 as required for the ECU K-line
• I can also switch it to pin 7, but ECU communication is supposed to be through pin 3
• KKL chip is marked FT232R
• Using FTDI drivers on a clean windows 7 machine with the required net framework

I've had issues with my v1.3 board since I bought it about a year ago. After trying countless fixes from this forum and Google. including registry edits, BIOS changes, and multiple official and unofficial drivers

Installing a specific Wi-Fi driver solved most of the issues. Bluetooth has been completely stable since then, and Wi-Fi works perfectly when the module is detected.

The only remaining problem is that, after some boots, the Wi-Fi module isn't detected at all. The only reliable fix is the "unplug and press the power button" method posted here years ago: shut down the PC, unplug the PSU, press the power button to discharge any remaining power, then reconnect . After that, the Wi-Fi module is detected and works normally.

is there any fix for this? can i rma de board?. before the unplug fix it was a nightmare , now atleast i know how to retrive wifi , its just a little annoying

I've had issues with my v1.3 board since I bought it about a year ago. After trying countless fixes from this forum and Google. including registry edits, BIOS changes, and multiple official and unofficial drivers

Installing a specific Wi-Fi driver solved most of the issues. Bluetooth has been completely stable since then, and Wi-Fi works perfectly when the module is detected.

The only remaining problem is that, after some boots, the Wi-Fi module isn't detected at all. The only reliable fix is the "unplug and press the power button" method posted here years ago: shut down the PC, unplug the PSU, press the power button to discharge any remaining power, then reconnect . After that, the Wi-Fi module is detected and works normally.

is there any fix for this? can i rma de board?. before the unplug fix it was a nightmare , now atleast i know how to retrive wifi , its just a little annoying

I've been running a billet wastegate actuator on my TD04HL-16T for a few months and can't get boost past 9 psi, no matter what spring or preload I use. It always falls off at mid to high RPM.

When I compared it to the stock actuator, I noticed the stock one only has about 10 mm of travel, while the billet one has around 15–20 mm. Could the extra travel be causing the wastegate to open too far and bleed off boost?

I've tried different springs, different preload settings, and even stock preload specs with no change.

My thought was to use a lighter spring and shorten the rod as much as possible so the wastegate can't open as far, while still keeping the correct preload. Does that make sense, or am I looking at this the wrong way?

Or is the ECU simply commanding the TCV to open the wastegate more for some other reason?

Car: 1996 Volvo 850 T5, almost Stage 0.

• Only codes are for bad ABS sensor readings.
• radiator is leaking (idk if it pulls timing for this)
• Turbo was rebuilt (not sure what was replaced, maybe just the CHRA).
• Fuel pressure set at 3.5–3.8 bar.