Register
Page 2 of 2 FirstFirst 12
Results 16 to 19 of 19
  1. #16
    DK Veteran
    rob h's Avatar
    Join Date
    May 2011
    Posts
    4,517
    Thanks Thanks Given 
    1,860
    Thanks Thanks Received 
    2,104
    Thanked in
    1,475 Posts

    Default

    Clone the transponder.

  2. #17
    Member
    Join Date
    Sep 2019
    Location
    Tacoma, WA
    Posts
    41
    Thanks Thanks Given 
    29
    Thanks Thanks Received 
    10
    Thanked in
    6 Posts

    Default

    I see you have experience with the SMOK JTAG device? I purchased one about a year ago. Trying to use it now on a 2002 Volvo V70 with the 28F400 style CEM. I get the good read out of the device, but when I load file into Tango or VVDI2 it says file unknown.... So I compared the data in VVDI Prog with a known working eeprom file from a another vehicle we did where we desoldered the chip and read out. It appears some of the data is flipped in the file. The question I have is, based on your experience with this device is that normal for the data to be flipped? And if so, what is the best way to correct this issue? We would like to resolve this as this is the least possible risk way to make keys for these vehicles. We contacted SMOK and explained this issue and sent the file we read out and they said the device was reading according to the manufactures specs...
    Attached Files Attached Files
    Last edited by Psl0cksm1th; 17th January, 2024 at 08:54 PM.

  3. #18
    DK Veteran
    fred77's Avatar
    Join Date
    Jun 2019
    Posts
    1,401
    Thanks Thanks Given 
    641
    Thanks Thanks Received 
    511
    Thanked in
    400 Posts

    Default

    Quote Originally Posted by Psl0cksm1th View Post
    I see you have experience with the SMOK JTAG device? I purchased one about a year ago. Trying to use it now on a 2002 Volvo V70 with the 28F400 style CEM. I get the good read out of the device, but when I load file into Tango or VVDI2 it says file unknown.... So I compared the data in VVDI Prog with a known working eeprom file from a another vehicle we did where we desoldered the chip and read out. It appears some of the data is flipped in the file. The question I have is, based on your experience with this device is that normal for the data to be flipped? And if so, what is the best way to correct this issue? We would like to resolve this as this is the least possible risk way to make keys for these vehicles. We contacted SMOK and explained this issue and sent the file we read out and they said the device was reading according to the manufactures specs...

    are you sure all data isn't fliped?

    It's common issue 16-bit (2 bytes) just how data is formatted/displayed. the larger byte either comes 1st or last in groups of 2 bytes.

    There may be option in smok if not do a google
    Solidarity with Ukraine

  4. The Following User Says Thank You to fred77 For This Useful Post:

    Psl0cksm1th (18th January, 2024)

  5. #19
    Member
    Join Date
    Sep 2019
    Location
    Tacoma, WA
    Posts
    41
    Thanks Thanks Given 
    29
    Thanks Thanks Received 
    10
    Thanked in
    6 Posts

    Default

    Quote Originally Posted by fred77 View Post
    are you sure all data isn't fliped?

    It's common issue 16-bit (2 bytes) just how data is formatted/displayed. the larger byte either comes 1st or last in groups of 2 bytes.

    There may be option in smok if not do a google
    Thank you for the suggestion! There was an option in Multiprog SMOK to swap under edit tab.

 

 
Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.