When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
To all the SDD veterans here, can anyone help me with what I am doing wrong in SDD while programming a new RCM?
Background: 2016 F Type base, crash damaged. I fixed up all the front end damage, 90% of it was bolt on parts. Now, I am trying to program a new RCM in the car using SDD (v164.0 Offline) and when I get to setting the module into normal mode, it fails the test.
Upon "continuing" a pervious session in SDD that had the original RCM installed, I installed the new RCM and initiated that session. Then went into configure new modules - RCM and went through the checkboxes and onscreen instructions.
SDD located the relevant SW files and flashed them on the new RCM and went through VIN learn just fine. Then on, checked if RCM was in delivery mode...it wasn't and passed the test. Afterwards, when SDD tries to set the module into normal operating mode, its fails.
Is there anything else I need to do? maybe the RCM needs to seat in its little den under the console? (sounds strange). SDD never ran RCM calibrations in regards to impact sensors or anything else during the setup process, which I feel like it should. Or do I need an active TOPIx programming subscription? I did just program a new DSM just fine without TOPIx.
At a complete loss here
Initial programming screen 1 Initial programming screen 2 Pre SW load module scan SW file scan on the new RCM SW flash onto new RCM SW flash verification VIN learn Module Initialisation Normal mode setup failure
Hi, I have completely the same trouble with the same errors in Jaguar XF. Could you guys advise on what direction to go next?
I couldn’t program the RCM myself through SDD on my laptop with mongoose. The same errors persisted.
User @Tech_JLR helped me remotely and after that I just had to run RCM angle calibration myself through SDD to get it all working again, and airbag lights to turn off.
Reach out to him!
An FYI - new members can’t PM until they’ve made 5 (or maybe 10) posts.
That's right, I'm new here and haven't reached 10 posts yet . I don't want to spam with stupid stuff, but I would love to hear from a friend .
Originally Posted by Blubbers
I couldn’t program the RCM myself through SDD on my laptop with mongoose. The same errors persisted.
User @Tech_JLR helped me remotely and after that I just had to run RCM angle calibration myself through SDD to get it all working again, and airbag lights to turn off.
Reach out to him!
Hi, after many attempts and a lot of time spent, we’ve finally found a solution to our RCM calibration issue. In short, we tried using different versions of JRL SDD (both online and offline 150-165), but this didn’t make any difference. We also used recommended VCI interfaces like GODIAG and Mongoose, and while each worked to some extent—reading, diagnosing, performing parts of the procedures from recommendations, Extras, and Service Procedures—they didn’t work for RCM.
The solution turned out to be simple in our case. In our last attempts, we bought an interface to perform programming via the TOPIX cloud, specifically the VXDIAG VCX SE. Although we couldn’t configure it with the cloud due to license issues, we decided to give it one last try and launched the Offline JRL version (just the first one I had configured). Using the VXDIAG VCX SE, the RCM calibration procedure worked perfectly and solved all our problems. The process went as smoothly as demonstrated in the video.
It seems that the other interfaces caused issues and interference in the CAN line, preventing us from completing most tasks. I hope this helps someone facing similar problems in the future.
Programming new RCM/SRS module using SDD, HELP!
. I don't want to spam with stupid stuff, but I would love to hear from a friend 
