On the Lamfa table starting address needs changed from 0x23732 to 0x23736. Was making adjustments to the table and the whole table started getting way out of wack. Everything else looks perfect! Thank you!!

Does any know how to remove the 1-2 torque limiter on a P1(ME9)? I got a S40 T5 AWD AUTO. So far, I've been looking at MDBGRG section and switched it off on the CWMDBGRG but is still limiting it.

Cwtrans needs to be either 04 or 00 for me7. I can’t remember exactly without my ols in front of me.

Thank you. I don't really have the exact CWTRANS address for this bin file but have one from a different car with similar pattern. I'm gonna go test it.

Does anyone have an Tune with Antilag/NLS Inside which works in every Mode?  Softwareversion could be GPHJ/GSJH something 05>

With Best Regards

From what I've seen, the difference is in EVAP.

I have some good news. I have almost completed the changes to Sardine that allowed me to talk to the RPI and turn it into a J2534 device. I had to refactor the code to make it work over TCP/IP, I had to also refactor the message handling mechanism to work with multiple messages in one recv operation. I had to write a small python proxy on the Pi , which is still very crude but allows me to spoof some CEM data to get VIDA going.

It took me a week simply because of the awful development environment I set up. Main PC with Visual Studio -> Laptop with VIDA -> RPI. Transferring from PC to laptop, refreshing the localhost/Vida instance via reloading or having to kill the IE tab emulator + needing to restart the RPI python server took a toll on my time. I can't even describe how many times my J2534 dll crashed(bad pointer arithmetic) and I had to manually kill all msedge processes.

All I have to do is wait for my raw OBD2 cable to arrive, set up a charger for my RPI in my car, and most importantly, find a way to relay the CAN messages to VIDA without blocking or saturating VIDA with too many.

Anyway, throughout all this I saw that on my test ECM on the bench, the DLC byte commonly seen here is irrelevant and doesn't actually work with the 2002 HN.2. Perhaps it only works when connected via the CEM.
So commands that should be 000FFFFE#CB7AXXXXXXXXXX do not work, but when removing the 0xCB byte(DLC field) it works just fine, or perhaps I wasn't sending it correctly.

I was working based on this information.

https://github.com/Alfaa123/Volvo-CAN-Gauge/blob/master/Diag_Request.png

Also, which areas do you feel I am lacking in, genuinely asking for constructive criticism so I can improve. However if I can say one or two things in my defense, it's that the information is fragmented between multiple websites, multiple languages, github repositories or forum pages. Even then some of it is subjective based on whoever wrote it and his or her understanding of it. It took me a long while to get to where am I now, even though important bits such as Sardine J2534 being there free to use and extend which saved me quite some time in and of itself. My last goal which I may fail is the bootloader for Denso-based ECUs. I am really surprised that only the subaru people ever went to explore those ECUs.

Anyway, just how many protocols do Volvo use? I mean there's a ton over CAN, ISO15765, K-line, UDS, a few more(quite a few), D2, GGD.