RAM 1500 Diesel Forum banner
121 - 140 of 830 Posts
Sorry, I don't know what the RFHub is. I just know that once I got the correct ECU in place, I was able to swap back and forth with the GDE ECU with no (driver visible) error codes or any other anomalies.
Ok well that's promising. The RFHub is part of another computer module in the truck that communicates with your key fob. You can only access it with a scan tool or using AlphaOBD.
 
Let me know how it goes, I ordered a bench flash set up also and just waiting on it to come. My plan is to bench flash to overwrite the VIN and also reset the flash counters back to 0. You are right with this set up in theory we should be able to make a 1 to 1 clone of the ECM even clone a GDE tuned ECM for safe keeping. I also was able to locate the stock ECM firmware for Ecodiesels that was dumped to a .bin file as well. We should be able to use this to program a stock ECU also. Did you order a Kess Ktag Master unit?
Just got in my KessV2 clone today. As I expected, the K-suite 2.47 that is packaged with all of the clones doesn't have the protocols to OBD read the EDC17C79. I believe you can probably crack open the ECM and do the bench program. I might poke around and see if I can find a newer "unofficial" k-suite version, but it doesn't look very promising. Need v3.26 or newer to use Kessv2.

As a side note, if someone is purchasing the legit tools, apparently you don't have to open up the ECM with K-tag as of Ksuite v3.31, but it's not clear if this is full access

https://www.alientech-news.com/en/k-suite-3-31/

This setup was recommended to me as an alternative by the linked website:

http://www.eobdtool.co.uk/wholesale/ktm-bench-ecu-programmer.html

If I could find it someone in the U.S. i would probably give it a chance.
 
I think as long as you have the newest Kess V2 you can use a newer Ksuite copy. I think the firmware has to be 5.017 and it should work and not brick the clone. I think Ksuite 3.59 is the latest.


Sent from my iPhone using Tapatalk
 
You people are amazing. This thread might as well be a foreign language to me, yet you converse like it’s a backyard bbq. I wish you pioneers the best! Appreciate the effort and knowledge.


Sent from my iPhone using Tapatalk
 
No one has had success with the current version of AlfaOBD AFAIK.

I've sent an email to the developer, one, asking if the VIN Write diagnostic works on any model. And then if so, can he help us out.

I also broke down and purchased a "european" KessV2 clone off of ebay. Might be a pile of junk.... we'll see. It was only $78 bucks and I can return it.
Wondered if you heard anything from the AlfaODB developer?
 
Cloned Kess units will not work for the edc17c79. Only the KTAG will do it. Bench flash is the only option.

Plus, if you do use the true and very expensive kess/ksuite it may update the flash counter. Obd2 access not as extensive as bench flash.
 
Wondered if you heard anything from the AlfaODB developer?
No I haven't. I just used the email assoicated with app support: info@alfaobd.com. I know some other folks here mentioned the developer by name. Is there a better way to get in contact with him?

On a side note, no one would happen to know anyone in europe with an ecodiesel would they? If we could find someone with an EDC17C49 to do a trial run and verify whether or not AlfaOBD is throwing a simple bounds error when we enter the VIN. Both the EDC17C49 and EDC17C79 use the same TC1779 infineon chip.
 
In the Autel video, they physically disconnected the key security module very near the ignition switch before they showed storing the new VIN. I'm wondering if this might be the trick needed for the AlfaOBD to work? We haven't (yet) tried this and the error message that we got when trying to store the new VIN was that the number was out of range. We even tried just changing only the very last digit of the original VIN - same error message. As stated previously, the AlfaOBD seemed to accept all of the new injector codes (which we all thought was going to be the hard part), but now we just need to get the VIN changed!!
 
No I haven't. I just used the email assoicated with app support: info@alfaobd.com. I know some other folks here mentioned the developer by name. Is there a better way to get in contact with him?

On a side note, no one would happen to know anyone in europe with an ecodiesel would they? If we could find someone with an EDC17C49 to do a trial run and verify whether or not AlfaOBD is throwing a simple bounds error when we enter the VIN. Both the EDC17C49 and EDC17C79 use the same TC1779 infineon chip.
I did not want to bother if other people had already covered that route or the developer had replied no. Interestingly enough I think someone worked with the injector codes question and he made a change to accept 7 digits instead of 9. Alfa vehicles in Europe use the 9 digit coding!

Comments in other forums lead me to believe if request are made the developer is pretty conductive to adding features.
 
I did not want to bother if other people had already covered that route or the developer had replied no. Interestingly enough I think someone worked with the injector codes question and he made a change to accept 7 digits instead of 9. Alfa vehicles in Europe use the 9 digit coding!

Comments in other forums lead me to believe if request are made the developer is pretty conductive to adding features.
I never saw a reply. It's possible it got caught in SPAM, but I checked to the best of my ability and never saw anything.
 
Called my local shop and asked about replacing the ECM. They work on my old diesel. They said they use a local guy who comes to you and programs the vin numbers. They are calling him to contact me. Have GDE and the original ECM on my shelf. Installed right after update. Hope it’s not a wild goose chase.

Image
Image



Sent from my iPhone using Tapatalk
 
Cloned Kess units will not work for the edc17c79. Only the KTAG will do it. Bench flash is the only option.

Plus, if you do use the true and very expensive kess/ksuite it may update the flash counter. Obd2 access not as extensive as bench flash.
Correct, I just received mine and unfortunately KSuite 2.47 does not work for a read out. I also just received my KTag 2.25 unit and can confirm this appears to have all the information needed to read out and flash the ECM. Just waiting on my donor ECM to arrive and will crack it open. It requires soldering 1 wire onto the boot pin of the Tricore Microprocessor. I am not concerned to do this as I have a ton of experience with surface mount soldering from repairing Apple laptops as part of my current work. Stinks we have to do that, even the newer KTag units no longer require cracking them open also. Have to work with what we got though. I will experiment with reading my donor ECM first and then backing it up and then trying to re-write the firmware just to get it down before attempting on my only ECM I have in my truck. Will keep everyone updated.
 
In the Autel video, they physically disconnected the key security module very near the ignition switch before they showed storing the new VIN. I'm wondering if this might be the trick needed for the AlfaOBD to work? We haven't (yet) tried this and the error message that we got when trying to store the new VIN was that the number was out of range. We even tried just changing only the very last digit of the original VIN - same error message. As stated previously, the AlfaOBD seemed to accept all of the new injector codes (which we all thought was going to be the hard part), but now we just need to get the VIN changed!!
I wondered this also, but the module your seeing in those videos is for older Dodge vehicles and is not relevant for these trucks, the RFHub module talks to the ECM and verifies the VIN number. The RFHub module is behind the rear passenger seat. From the wiring diagrams I have looked at it doesn't seem we can unplug anything at the key switch to bypass the communication, as it all needs to be tied together for the key to turn the truck on to the ACC position for AlphaOBD to even work and communicate with the ECM. See attached PDF for theory of operation. So it seems at least to me this was an older method to fool the ECM into being programmed on the older vehicles.
 

Attachments

you shouldn't have to soldier... get a BDM frame. makes it MUCH easier. no soldiering.
The EDC17C79 pins can be hooked up via the pin headers on the connector side of the ECM but there is a boot pin that requires being hooked up. I don't really think I will need a BDM frame for this since its just one pin. I ordered a set of pogo pins and a set of helping hands that should keep that pin in place on the 1 boot pin I need to access board side. Think I might give that a try.
 
The engine WILL start and will run ~3 seconds and then it will shut down if it doesn't have the right VIN.
This is the IMMO turning the engine off. You have 2 options:
1. Turn off the IMMO (get a tuner to do this)
2. Program the VIN

yes it'll run (not as well) without changing injector codes. It'll default to injector 1 code for all 6 injectors unless you've properly programmed them.
 
Hello all,

Some of you saw the conversation discussed in the GDE thread last week where we talked about using AlphaOBD to program injector codes and the Vin into another ECM. I have another ECM, and alphaOBD so I can give this a shot. The VIN is really straight forward and I'm ready to do this, however I wanted to reach out for some assistance on the injector codes. In AlphaOBD, it has the location to enter a 9-character injector value. Looking at the injector code on my engine, I'm not seeing 9 digits and am assuming its within the codes on the sticker. Does anyone know which 9 characters I should enter? I've attached screenshots

Thanks.

injector codes are easy, 7 digits followed by 1 - injector "1", then 7 digits - 2 "injector 2" and so on. Leave a space after 7 digits when programming them so the "8th" number would be 1,2,3...and so on.

There's SFT out there offering this service, remotely with their ECU device for $150. VIN/injector programming. All via OBD, remotely using official FCA Witech software (they're licensed)
 
There's SFT out there offering this service, remotely with their ECU device for $150. VIN/injector programming. All via OBD, remotely using official FCA Witech software (they're licensed)
I'm assuming you added this last bit. What your are stating is true; however some folks do not what the SFT tune. I think the original post was an attempt to transfer a GDE tuned ECM to another vehicle.

I haven't asked if SFT would JUST do the vin/injector programming an ECM. You would still have to have a compatible J2534 device. It appears that SFT ships the Tactrix Openport 2.0 which is $169 on its own.

https://www.tactrix.com/index.php?o...ge=shop.product_details&product_id=17&vmcchk=1&Itemid=53&redirected=1&Itemid=53

I will commend SFT on the solution they have come up with; I foresee a lot of companies mimicking the business model in the future. Provide a simple tool to the majority of your customers and handle the heavy lifting on the tuning providers end. What I don't like is the fact that currently your stock tune is stored on a remote server somewhere that, as far as I know, has no service guarantee.
 
Received a response from AlfaODB, writing a VIN may be fixed in the future [emoji6]

I heard about the VIN write issue, I’m working on a solution. Can’t promise anything now as this requires certain investigations, hopefully the fix will be available in one of the next updates.



Best regards,

Alexey Chernikov

AlfaOBD



Sent from my ONEPLUS A6010 using Tapatalk
 
121 - 140 of 830 Posts