Need Help From Eepromers

Post files somewhere if you can friend

Lots of possibilities….. Did you check that the VIN is not repeated a second and third time in different locations? Did you try off-board programming? How about programming voltages, correct pin contacts etc…. The “new” VIN in the first location seems to be missing a digit?

I'd check with Keith @L1 Diagnostics if you can't get any resolution. My guess is he's seen this more than once given he and his techs are serving actual shops on a daily basis.

Did you scroll all the way through the buffer editor and make sure the VIN is not repeated? Often times there is more than 1 VIN entry in the ECM.

The scanner maybe reading the VIN from a different module.

I’m no help on this one, but I was wondering what connection the AR32 uses to interface with your laptop. I looked on their website and didn’t see anything about this. USB, VGA, HDMI?

Andrew, AR32 uses a Old Fashioned Parallel Port for the connection to PC- They do sell a adapter of some sort. Otherwise the older tough books have the parallel connection.

You appear to have the right numbers… just in the wrong order. programming error? Also AR labs customer support is great. if you give them a call they might be able to figure it ou.

Ar32 is working correctly, it‘s just that the VIN string has to be interpreted differently. Start from the original back-up and try this: diag​.​net/file/f11flse1z… ​

Dimitri could you resend the changes with the correct vin? the one ending in 2634?

The translation above was made for 4S4BP62C…, have you tried it and got a different result on the scanner?

Hi Dmitriy, Can I ask how you perform the translation?

I’ll wait for Enrique to try it. If it works as intended, I’ll explain…

It looks like part of the vin is byte swapped. edit. Never mind. it’s not byte swapped. The first character is moved to the end.

Did you record the original vin of donor pcm with a scanner. Look like they “coded” the vin. It appears that they swapped each pair of characters.

So the original vin of pcm as taken from eeprom does not decode in identifix. This is a ”coded” or “encrypted” vin. Dmitriy know what to do but I think he did it on the wrong vin! If you can enter in the original vin back into the pcm and power up pcm on bench, then you can use a scanner to read “unencrypted“ vin. You can then compare the two vins to figure out the “encryption“. I dont know if…

no i did not, I'm planning on reloading the original vin and take readings and experiment a little next time i have car in shop

I noticed a pattern between the correct vin and the one the scan tool showed I would try this 4S2B467C…

Enrique, Add/write the data as shown in the image below in to the eeprom and it should read correctly on the scan tool.

thanks, will contact customer to bring back vehicle. I''ll keep you posted

Walter, Can you explain how you get this? Thank you!

Kerry, As other have stated it's byte swapped. Every 2 characters are inversed going down the to the end. Since the VIN has 17 digits and to make it an even pair you would add a space the last 2 characters would be 4 and a space which would then be a space and 4 when inverted. That is why there's a space between 6 and 4 at the end. So VIN 4S4BP62C… would look this way in the EEPROM data…

Hello Enrique,, You may or may not be aware of. - The donor ECM VIN is completely invalid, multiple wrong characters – indicates it’s been hacked previously, or possibly a foreign VIN - Trying to use an 08 ECM PN in an 07 car. – no valid overlapping PNs exist between 07 and 08 Outback Limited models. The wrong hardware. (assuming foreign VIN, the 10th digit is 8 -2008) - ECMs VIN rewriting…

Hi Donny, what Enrique listed as donor’s VIN was just a string from EEPROM. It had to be translated first. This is the printout for the actual donor’s VIN: 4S4BP60C… diag​.​net/file/f4amhms2g… ​ Does this record look OK, or something is suspicious about it? P.S. The vehicle Enrique has in the bay has VIN 4S4BP62C… — seems to be 2008 too? 2007 might be a typo?

Dmitriy Thank you for that clarification. With the title saying 2007 my eyes saw the VINs that way too and transposed the digits. Still, after a little checking it is the law in California that the seller is responsible for the SMOG pass. Of course that should have happened prior to exchanging money and who among us has not done the Post-Purchase inspection or emissions failure? It seems…

Very good points, Donny! I only saw a computer science puzzle in the original question, but there is a lot more to it for sure.

And this is why multiple view points and stakeholders result in better information. :)

Donny, on a different note; everybody including myself are having a hard time with the new SPS2 from GM, since I understand you might have some contacts on engineering could you ask them why the incredible amount of bugs? why not leave access to the old sps until thy figure out all of them?. Sorry to involve you in the mess it is obviously not your obligation, but I have heard (or read) that you…

Correct, my typo, vehicle is 2008

Original ECM not available, purchased AS IS by customer, can't really tell if the current ECM is a valid part number for the vehicle however the vehicle runs fine with no codes or other issues. I haven't research much on it, simply jumped on the eeproming wagon since I need the experience and is the most handy solution at the moment. If unable to fix VIN for customer then we'll have no other…

You could also send the customer to a SMOG referee. I would have all the monitors ready for their appointment.

With AR Labs on those chips you need to hit the letter ‘B’ on your keyboard and ‘B=Swap Bytes’ before modifying the VIN. After you swap bytes and modify the VIN, make sure you swap bytes again before writing it back to the chip. I have a file from one of those chips laying around so I pasted your VIN into it and then used the swap bytes function to show you what it looks like. Screenshots…

Thank you Brian, I will do as instructed tomorrow.

Brian thank you very much sir.!!! I performed the bytes swaps as described and it worked perfect!!! I'm calling this a closed case. thank you all for your input, Now we all have learned something new.

Good work and thanks for the follow up Enrique!