VS M4.4 tuning dead? Start again here?

[rkam]

You can use the standalone flasher from Motronicsuite for flashing M4.3 and M4.4.
http://www.villacarlota.net/volvo/motro ... index.html
http://www.villacarlota.net/volvo/index.html

M4.3 flash can be read in like 45 minutes through K-line.
http://volvospeed.com/vs_forum/files/fi ... 9-08-2010/

On M4.4 you can read the last 64kB (64-128) the same way. To get another 32kB (32-64) you need some more risky manouvers.
To get the first 32kB you need to open the box and short circuit one of the address pins.

[Chuck W]

You need a separate TP instance open for the M4.3 stuff. The default TP CheckSum plugin should be included in the install of TP. Also, Motrionic Suite works for flashing the M4.3 stuff.

No way to read current info without the Willems.

[GranTouringRacing]

RKam,

Thanks for this i had it all this ironically (except VolvoDiag) and when i reread the instructions for 4.3 i realised the XDF files cannot be used on Motronic Suite for 4.3.

The only thing i can get Motronic Suite to do is write the flash on 4.3 and 4.4 (and the Checksum which is handy), neither will communicate with the programs and the same for that VolvoDiag, the 4.3 won't communicate at all, the 4.4 will recognise its KWP71 and gets a keyword, it comes up with some numbers on test but once the 4.4 is connected all the buttons are unhighlighted and you cannot do anything.

I tried various compatibility tests and tried windows 8,7 and even XP to see if it was a dated issue but the only thing i can do with a 4.3 is write a flash, which is fine but if that actually worked where i could read the EEPROM it would be awesome, especially for 4.4.

I'm wondering if it's maybe the VAGCOM cable?

My old VOL-FCR uses the serial VAGCOM, could that be possible issue.

One of my biggest problems was all my files downloaded to Dropbox originally so the file path was actually trying to take them off dropbox even althought they were downloaded to the desktop, but when i sorted that i fixed the major issues.

I'm just confused how none of the comms functions work when they flash okay, the realtime menu's in Motronic Suite should read flash and DTC's etc but neither 4.4 nor 4.3 will connect on these either?

So any ideas how to get these to work would be great, thank you?

Cheers,
Scott.

You can use the standalone flasher from Motronicsuite for flashing M4.3 and M4.4.
http://www.villacarlota.net/volvo/motro ... index.html
http://www.villacarlota.net/volvo/index.html

M4.3 flash can be read in like 45 minutes through K-line.
http://volvospeed.com/vs_forum/files/fi ... 9-08-2010/

On M4.4 you can read the last 64kB (64-128) the same way. To get another 32kB (32-64) you need some more risky manouvers.
To get the first 32kB you need to open the box and short circuit one of the address pins.

[rkam]

I assume the correct pins are connected, and bootpin does NOT have power. Then it should be possible to connect, but sometimes a few retries is needed. Modern windows versions might decide to do other stuff in between, and then the Motronic will give up waiting and close connection.

[GranTouringRacing]

Ah,

Right for diagnostics and reading etc, it should not be in boot mode?

I think thats the problem if so?

I assume the correct pins are connected, and bootpin does NOT have power. Then it should be possible to connect, but sometimes a few retries is needed. Modern windows versions might decide to do other stuff in between, and then the Motronic will give up waiting and close connection.

[rkam]

Yes. The ecu should be in normal running mode for diagnose and reading.

[GranTouringRacing]

So disconnected the power supply to the B8 pin to stop boot mode and still doesn't work, the expected keywords are not the same as what comes through, then it times out, i noticed on 4.3 it wants diagnostic pin 3???

4.4 wants pin 7 which is the KLine, but when the boot mode is active it seem to connect but freezes but keeps getting different keywords everytime it tried to connect and both 4.3 and 4.4 still do not connect on motronic suite, i even downloaded on a completely separate computer and they are exactly the same.

Is that VolvoDiag for in car OBD or something then as i feel something just isn't right?

I cannot get any bench information off these ecu's anyway!

Yes. The ecu should be in normal running mode for diagnose and reading.

[rkam]

I will have to find some old notes, or try again myself. It has been many years since I made that program.
If the M4.3 is in a car, I believe the K-line of the ecu is connected ton pin 3 in the obd connector. This needs to be connected to pin 7 in a kkl- interface. But it should work on the bench. I have never had a car with M4.x

You might also try to reduce or change the buffer size of the serial port in Windows Device Manager
I've purchased a lot of cheap KKL-interfaces over the years, and some has given better signal quality on the K-line than others.

M4.4 at 0x10: Key Bytes 0xAB 0x02 pin B36 old type 9600bps (KWP)
M4.4 at 0x33: Key Bytes 0x08 0x08 pin B36 OBDII ISO9141-2 10400bps
M4.4 at 0x7A: Key Bytes 0xD3 0xB0 pin B36 Volvo special 10400bps used by VST
M4.4 bootmode pin B36 9600bps

M4.3 at 0x10: Key Bytes 0xAB 0x02 pin B5 old type 12500bps used by VST (On PC 12700 might be used if 12500 is not accepted)
M4.3 at 0x33: Key Bytes 0x08 0x08 pin B36 OBDII ISO9141-2 10400bps
M4.3 bootmode pin B5 9600bps

[GranTouringRacing]

RKam,

I didn't realise you wrote the program!

So obviously on the bench set up my KLine is set up to pin 7 on an OBD connector on the VAGCOM, does the pin 3 need to be attached for 4.3, is this trying to read KLine through pin 3 on the OBD then?

On the program it does say pin 3 for 4.3 and pin 7 for 4.4.

What is getting me is Motronic Suite (did you write this too?) the comms do not work for either ECU either, but all systems write the flash using my set up with boot mode activated.

What it seem like is the expected response of keywords is not what the ecu's are giving to the program 0xAB 0X02 so expected keywords being AB 02 yet on the 4.4 it gets FF FF with detected protocol of KWP71 then serial timeout and then closes.

Just literally tried the 4.3 to see what it was doing and miraculously it's now working lol?

Trying the EEPROM dump, 'please wait a very long time' lol, but that is awesome if this works, really need the 4.4 to work and then i have a way to read the maps, which is a total game changer!

I really appreciate this help by the way.
Scott.

I will have to find some old notes, or try again myself. It has been many years since I made that program.
If the M4.3 is in a car, I believe the K-line of the ecu is connected ton pin 3 in the obd connector. This needs to be connected to pin 7 in a kkl- interface. But it should work on the bench. I have never had a car with M4.x

You might also try to reduce or change the buffer size of the serial port in Windows Device Manager
I've purchased a lot of cheap KKL-interfaces over the years, and some has given better signal quality on the K-line than others.

M4.4 at 0x10: Key Bytes 0xAB 0x02 pin B36 old type 9600bps (KWP)
M4.4 at 0x33: Key Bytes 0x08 0x08 pin B36 OBDII ISO9141-2 10400bps
M4.4 at 0x7A: Key Bytes 0xD3 0xB0 pin B36 Volvo special 10400bps used by VST
M4.4 bootmode pin B36 9600bps

M4.3 at 0x10: Key Bytes 0xAB 0x02 pin B5 old type 12500bps used by VST (On PC 12700 might be used if 12500 is not accepted)
M4.3 at 0x33: Key Bytes 0x08 0x08 pin B36 OBDII ISO9141-2 10400bps
M4.3 bootmode pin B5 9600bps

[rkam]

Motronicsuite is made by Dilemma.
I've helped him with information on K-line communication and M.4x hardware.
Dilemma helped me a lot with Volvodiag which is C++ based on a program Omegadiag.
My own tools was before this written in Visual Basic.
Although I was able to implement Volvo protocols in the C++ program, I quickly got into trouble dealing with Windows GUI stuff.
Therefore I have kept the buttons that doesn't work on Volvo in case I need them for something else.
Replacing the program code I can manage, but adding a button is much more difficult for me.

Lately I have been using Tiny C Compiler for command line tools with DiCE.

Communication in Motronicsuite seems to be more difficult to make and keep running.
Motronicsuite is programmed in C Sharp, while Volvodiag is in C++.
Maybe C# is more affected by Windows functions stealing time.