How To Use AlfaOBD On 2025+

[JDHarris]

You don’t do anything with the 30 day VIN license as far as assigning it. It will automatically get assigned to the first vehicle you connect witech to.
There isn’t a setting for the pressure thresholds. I believe that is handled in the RF Hub now. On your witech topography, click miscellaneous functions, and see if there’s anything related to RFH tire pressure there, and if it can be edited:
View attachment 211801

I didn’t even think to check in WiTech for that. I was looking in AlfaOBD. Thanks for the suggestion. I’ll check this afternoon and report back.

For the license, I didn’t see any way to connect without a license being linked. MoparTSP showed a VIN license ready to use, but WiTech said there was no license and clicking the vehicle did nothing. As soon as I got the 3 day license, it updated and let me assign and get into the vehicle. The VIN license is still sitting there unused. I’ll try that again after the 3 day expires.

Thanks!

 

[JDHarris]

EDIT: I was using a splitter and unlocking the security gateway with Anyscan. Having the second device connected seems to be what caused the issues with WiTech2. Using only WiTech2 with either Rlink device (X7 or J2534) seems to work as epected. WiTech2 can unlock the security gateway on its own and does not need a splitter and second device (thanks for helping me identify that).

Original message:

Just following up. WiTech2 SUCKS to use. Sometimes it takes 20 minutes to scan the truck, sometimes it takes an hour and a half and never seems to complete. It gives no real indication of progress or activity. Lots of “please wait…”.

WiTech2 does not detect the RF Hub, so I can’t change settings on it. Anyscan does detect the RF Hub and lets me view all the live data, but can’t change any values. No options in AlfaOBD to change the values.

So, it seems you can adjust tire circumference to calibrate the speedometer, but I have not found a way to change the TPMS thresholds.

The iteration time when experimenting is slooooooooow. Be prepared to wait a long time for almost every operation in WiTech2. I’ve had to keep a charger on to do this. Otherwise the times are long enough you run the battery below 12v and the truck forces everything off.

The truck will automatically go from the run position to off about every 15 minutes as well. Be prepared to push the start button again at that point and hope whatever WiTech2 is doing is still okay. It usually won’t tell you if it screwed up though. It just won’t complete.

If you are a low patience person, take it to the dealer for the proxi alignment. Yes, I see the irony!

 

[Jimmy07]

Just following up. WiTech2 SUCKS to use. Sometimes it takes 20 minutes to scan the truck, sometimes it takes an hour and a half and never seems to complete. It gives no real indication of progress or activity. Lots of “please wait…”.

WiTech2 does not detect the RF Hub, so I can’t change settings on it. Anyscan does detect the RF Hub and lets me view all the live data, but can’t change any values. No options in AlfaOBD to change the values.

So, it seems you can adjust tire circumference to calibrate the speedometer, but I have not found a way to change the TPMS thresholds.

The iteration time when experimenting is slooooooooow. Be prepared to wait a long time for almost every operation in WiTech2. I’ve had to keep a charger on to do this. Otherwise the times are long enough you run the battery below 12v and the truck forces everything off.

The truck will automatically go from the run position to off about every 15 minutes as well. Be prepared to push the start button again at that point and hope whatever WiTech2 is doing is still okay. It usually won’t tell you if it screwed up though. It just won’t complete.

If you are a low patience person, take it to the dealer for the proxi alignment. Yes, I see the irony!

What pass thru device are you using for witech?
How’s your WiFi signal? Are you using home WiFi, or tethering to your phone?

 

[JDHarris]

What pass thru device are you using for witech?
How’s your WiFi signal? Are you using home WiFi, or tethering to your phone?

I’m using the TOPDON X7 and connecting to home WiFi (2Gbps). From your question, I’m assuming that behavior isn’t your experience? On average, it’s about 40 minutes to get WiTech2 to do something. What should it take?

 

[timbottorff]

I'm sorry if this was already addressed in another thread but will this work to get the trailer 360 cameras working correctly (not through Aux 1) on a 2026 Ram 2500?

 

[Abhi.K]

I’m using the TOPDON X7 and connecting to home WiFi (2Gbps). From your question, I’m assuming that behavior isn’t your experience? On average, it’s about 40 minutes to get WiTech2 to do something. What should it take?

Usually it takes around a minute to do anything unless you are running a procedure that takes a couple of minutes but even then you will see a moving status that changes over time. But those response times you have are way too high. The only difference is i use the rlink j2534 and not the x7. So far it has been quick for me on both Atlantis and Powernet vehicles. I had someone else have issues with x7 and i did see their witech kinda be slow when i was helping them so it could be a vci thing. They even had a flash fail with module and it was stuck with x7 acting bricked. But they had a buddy with cardaq 3 and using that has solved their issue.

 

[Jimmy07]

I’m using the TOPDON X7 and connecting to home WiFi (2Gbps). From your question, I’m assuming that behavior isn’t your experience? On average, it’s about 40 minutes to get WiTech2 to do something. What should it take?

Yeah, it shouldn’t be that long at all. It sounds more like the x7 isn’t going to be a recommendation for this anymore, and might have to go with the topdon RLink j2534

 

[Jimmy07]

I'm sorry if this was already addressed in another thread but will this work to get the trailer 360 cameras working correctly (not through Aux 1) on a 2026 Ram 2500?

Yes it’ll work, although I haven’t done a comparison between a truck that has it vs a truck that doesn’t so I can pick out the settings required for it.

 

[JDHarris]

Yeah, it shouldn’t be that long at all. It sounds more like the x7 isn’t going to be a recommendation for this anymore, and might have to go with the topdon RLink j2534

I have a Rlink J2534 that I can test later tonight. Glad to know my experience isn’t normal and I can stop beating my head against this wall.

 

[JDHarris]

It's starting to look like either the Rlink devices don't like the splitter, or I have a bad one. If I plug either the RLink X7 or the J2534 directly into the truck with no OBD splitter, then WiTech2 is responsive. It takes about a minute to load the configs, and operations within are relatively snappy.

With plugging it in directly, it seems I get more information from the truck as well. More ECUs are identified, including the RF Hub, which does let me change the tire pressures for TPMS.

That said, I'm not calling success just yet. I'm running through the PROXI Config alignment now. It's been at 6% for about 5 minutes. We'll see what happens. I expect it will fail though, since I don't have the second device unlocking the security gateway. That said, I was able to change the TPMS settings without it being unlocked (only the RLink device was plugged in).

 

[Abhi.K]

What are you using the splitter for? Witech doesn’t like other devices connected in parallel and locks sgw out and does kinda like a lockout mode which would explain the behavior you are seeing with it.

 

[JDHarris]

What are you using the splitter for? Witech doesn’t like other devices connected in parallel and locks sgw out and does kinda like a lockout mode which would explain the behavior you are seeing with it.

I was following the directions (I thought?) on the first page of this thread that said you need to use Anyscan to unlock the security gateway. Is that only for AlfaOBD, and not necessary for WiTech2?

PROXI configuration alignment doesn't appear to be working correctly yet. It made it through a few modules, but seems to be stuck on one. The first time through, it halted at 29% and did not proceed. Subsequent runs stop at 6%, which appears to be the first module it's attempting. If the order is the same as in the confirmation list, it's something called the ORC module?

 

[Abhi.K]

I was following the directions (I thought?) on the first page of this thread that said you need to use Anyscan to unlock the security gateway. Is that only for AlfaOBD, and not necessary for WiTech2?

PROXI configuration alignment doesn't appear to be working correctly yet. It made it through a few modules, but seems to be stuck on one. The first time through, it halted at 29% and did not proceed. Subsequent runs stop at 6%, which appears to be the first module it's attempting. If the order is the same as in the confirmation list, it's something called the ORC module?

Correct. Alfa needs the xtool with splitter to unlock SGW. Witech can do its own unlock with subscriptions and doesn’t need anything else connected. If it even senses anything in parallel it locks itself out.

I haven’t tried witech recently but back in November when i did it with rlink on WL for ORC (airbag) module replacement it did do the whole vehicle proxi alignment no issues and fixed all errors i has with BSCM(ABS) module and other modules.

[mention]Jimmy07 [/mention] will know more on this since he did this recently on new 25+DT.

I did have another person with x3 or x7 try this but it wouldn’t do proxi alignment and he ended up with bricked module because he had a immobilizer that interrupted CAN bus during witech flash and his rlink couldn’t reflash it in witech after initial failure. It would detect the module but wouldn’t run flash and would be stuck on flash screen. He ended up using cardaq from a buddy which fixed his issues with bricked module after he removed that immobilizer wiring completely. If you have anything aftermarket setup that uses CAN bus i would suggest removing or disabling it since it can cause witech procedures to not run.

 

[JDHarris]

Correct. Alfa needs the xtool with splitter to unlock SGW. Witech can do its own unlock with subscriptions and doesn’t need anything else connected. If it even senses anything in parallel it locks itself out.

I haven’t tried witech recently but back in November when i did it with rlink on WL for ORC (airbag) module replacement it did do the whole vehicle proxi alignment no issues and fixed all errors i has with BSCM(ABS) module and other modules.

[mention]Jimmy07 [/mention] will know more on this since he did this recently on new 25+DT.

I did have another person with x3 or x7 try this but it wouldn’t do proxi alignment and he ended up with bricked module because he had a immobilizer that interrupted CAN bus during witech flash and his rlink couldn’t reflash it in witech after initial failure. It would detect the module but wouldn’t run flash and would be stuck on flash screen. He ended up using cardaq from a buddy which fixed his issues with bricked module after he removed that immobilizer wiring completely. If you have anything aftermarket setup that uses CAN bus i would suggest removing or disabling it since it can cause witech procedures to not run.

Thank you for the information. That all makes sense with what I was seeing.

I have nothing aftermarket that touches the CAN bus. Only additions that are electrical are 12v things like lights and a compressor. It did get interrupted the first time because it stayed at 29% long enough for the vehicle to turn itself off from the RUN position.

 

[Jimmy07]

Thank you for the information. That all makes sense with what I was seeing.

I have nothing aftermarket that touches the CAN bus. Only additions that are electrical are 12v things like lights and a compressor. It did get interrupted the first time because it stayed at 29% long enough for the vehicle to turn itself off from the RUN position.

Yeah, don’t use a splitter with witech, like mentioned above. Technically, a splitter changes the termination resistance on the diagnostic CAN lines, since they are wired in parallel to make two ports, and witech doesn’t seem to like that.

 

[JDHarris]

I was able to do the PROXI alignment using a Cardaq VCI. For whatever reason the RLink devices would get stuck at various points.

Now that it's completed, there were 4 modules that reported an error status during the PROXI Config alignment. The message listed was "No communication" for all of them. The modules were DTCM, SAM, BSCM, ITCM. Is this expected? It’s still saying DTC B2204-00 is still active, which I presume is related to the above error.

Steps taken: PROXI config alignment, disconnect everything, power off truck, open door, close door, leave truck sit for 30 minutes, power cycle truck 4 times and wait 60s on last one, clear DTCs with WiTech2.

I’ve repeated this a couple times with the same result. My changes don’t seem to be reflected (tire circumference and tire placard pressure) and the odometer is still flashing and things like ABS are still throwing errors on startup.

 

[Abhi.K]

I was able to do the PROXI alignment using a Cardaq VCI. For whatever reason the RLink devices would get stuck at various points.

Now that it's completed, there were 4 modules that reported an error status during the PROXI Config alignment. The message listed was "No communication" for all of them. The modules were DTCM, SAM, BSCM, ITCM. Is this expected? It’s still saying DTC B2204-00 is still active, which I presume is related to the above error.

Steps taken: PROXI config alignment, disconnect everything, power off truck, open door, close door, leave truck sit for 30 minutes, power cycle truck 4 times and wait 60s on last one, clear DTCs with WiTech2.

I’ve repeated this a couple times with the same result. My changes don’t seem to be reflected (tire circumference and tire placard pressure) and the odometer is still flashing and things like ABS are still throwing errors on startup.

Thats odd but seems like the failing modules you listed need ignition to be in RUN mode for those to work. Did the ignition time out and shut off during proxi alignment. I would expect cardaq to work since its witech verified official device.

The errors you have and flashing odometer is definitely failed proxi issue. Did you change tire size too? If so you would need to rerun abs initialization procedure and then clear all codes and then do the proxi process. Someone that did mess with tires mentioned the abs initialization was needed to clear all the codes and issues.

Maybe even disconnect battery for an hour or so to reset all system to clear all failures then do abs and proxi procedures to see if it all passes.

 

[JDHarris]

Thats odd but seems like the failing modules you listed need ignition to be in RUN mode for those to work. Did the ignition time out and shut off during proxi alignment. I would expect cardaq to work since its witech verified official device.

The errors you have and flashing odometer is definitely failed proxi issue. Did you change tire size too? If so you would need to rerun abs initialization procedure and then clear all codes and then do the proxi process. Someone that did mess with tires mentioned the abs initialization was needed to clear all the codes and issues.

Maybe even disconnect battery for an hour or so to reset all system to clear all failures then do abs and proxi procedures to see if it all passes.

Thanks for the suggestions. I’ll try them out. I did change tire circumference.

I tried reverting the 3 changes (tire diameter and front/rear TPMS threshold) I made and re-running proxi alignment to get back to factory state, but I’m still getting the flashing odometer and proxi misalignment error code after this.

There were no interruptions on the proxi alignment process and the truck was in run mode with the engine off and radio on.